memo_get

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

With no annotations provided, the description must fully disclose behavioral traits. It only mentions the return value ('detailed memo information including content, metadata, and relationships') but does not disclose side effects, permissions, error behavior, or read-only status. Minimal transparency beyond the return payload.

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?

Two sentences, front-loaded with the core action and resource. Every word earns its place; no fluff or redundancy. Highly concise.

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 single-parameter get operation, the description adequately covers the purpose and return value. The tool has no output schema, so mentioning 'content, metadata, and relationships' helps the agent understand the response. Missing error handling or not-found behavior is not critical for this simple 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?

Schema coverage is 100% with the memoId parameter described as 'ID of the memo to retrieve.' The description adds the adjective 'specific' but no additional semantic detail such as format or examples. Baseline 3 is appropriate when the schema already documents 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 clearly states the tool's function: 'Retrieves a specific memo by its ID.' The verb 'retrieves' and the resource 'specific memo by its ID' distinguish it from siblings like memo_list (likely retrieves many) and memo_search (likely query-based).

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 usage when you have a memo ID and need detailed info, but it does not explicitly mention alternatives or when to use sibling tools. No exclusions or when-not-to-use guidance is provided, so the guidance remains implied rather than explicit.

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