get_memo

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

With no annotations, the description alone indicates this is a safe read operation that returns full memo content, but it doesn't disclose behavior when the ID doesn't exist, whether permissions are required, or whether the response shape differs from list_memos. These are common gaps for a getter.

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?

A single, front-loaded sentence states the action, resource, and distinguishing scope without any filler or redundancy. Every word contributes to understanding what the tool does.

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 one-parameter getter with an output schema, the description provides the essential retrieval semantics. It lacks explicit differentiation from search_memos and error-behavior details, but those are minor for this straightforward tool.

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 schema has 0% description coverage, but the description explicitly ties memo_id to 'by ID', so the agent knows the parameter selects the memo to retrieve. This adds minimal meaning beyond the parameter name and satisfies the basic expectation for a single self-explanatory 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 uses a specific verb ('Retrieve') and names a clear resource ('full details and content of a specific memo by ID'). This distinguishes get_memo from list_memos and search_memos: it targets one memo by its identifier rather than returning a collection or matching a query.

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 implies the tool is for fetching a single memo when the memo_id is already known, but it doesn't explicitly say when to prefer get_memo over search_memos or list_memos. No alternative routing or exclusion is provided.

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