memoryguard_knowledge_read

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no read-only confirmation, no effects, no return format, no pagination or versioning behavior. The only hint of non-mutation is the verb 'read' in the tool name, which the description itself never confirms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words is brief, but this is under-specification rather than disciplined conciseness. The phrase 'V2-native knowledge surface.' is jargon that does not earn its place — a short description only scores well when its few words actually inform, and these do not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the agent's only source of context, and it provides essentially none. A read tool needs at minimum a statement of what is read and what is returned; 'V2-native knowledge surface.' is completely inadequate for that purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, so there is nothing for the description to document beyond the schema, which is trivially complete. Per the baseline for zero-parameter tools, this dimension is satisfied even though the description adds no parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'V2-native knowledge surface.' contains no verb and no concrete resource — 'surface' is an unexplained metaphor and 'V2-native' is a version tag, not a functional statement. The tool's actual behavior (reading knowledge) is only inferable from its name, and nothing distinguishes it from siblings like memoryguard_knowledge_list, memoryguard_knowledge_search, or memoryguard_memory_read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to invoke this tool versus any of its 60+ siblings. No context, no exclusions, no alternatives — an agent cannot determine whether knowledge_read, knowledge_search, knowledge_list, or memory_read is the right choice without opening other definitions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.