project_memory

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that it reads memory drafts and reviews state/freshness, but does not explain output, pagination, freshness semantics, or the odd 'stored procedures' caveat. It adds some context but not rich behavioral detail.

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?

The description is very short and front-loads the read action, which is good. The second sentence is somewhat cryptic and may not earn its place, but the overall structure avoids verbosity.

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?

For a simple read tool with one parameter and no output schema, the description still omits any explanation of include_retired, return content, or distinction from sibling memory tools. Annotations cover safety, but the definition is too incomplete for confident selection and invocation.

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 one parameter, include_retired, with 0% schema description coverage. The description never mentions or explains this parameter, retired items, or how drafts relate to retired state. The description provides no semantic value for the parameter.

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 states a verb ('Read') and a resource ('memory drafts'), and adds that it reviews state and freshness. However, 'memory drafts' is vague, and the description does not distinguish this tool from close siblings like search_project_memory, project_memory_history, or recall_project. The second sentence does not clarify the core purpose.

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?

There is no explicit guidance about when to use this tool versus alternatives. The sentence 'Stored procedures are not execution permission' is a cryptic caveat, not a usage condition. An agent is left to infer when this tool should be selected.

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