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

With no annotations, description clarifies one row is stored and nothing else persists, which is transparent. Does not elaborate on permissions or error conditions, but sufficient for a submission tool.

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 concise sentences with no filler. Front-loaded with core purpose, then details, then outcome. Every sentence adds value.

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 tool without output schema, description explains storage and callback mechanism. Complete enough given sibling complementarity. Could mention response format but not needed.

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 covers 100% of parameters with descriptions. Description adds meaning to 'kind' (decides what gets built next) and 'channel' (for hearing back), enhancing baseline of 3.

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?

Description uses specific action 'tell the store why you came' and identifies resource types (unmet_need, introduction). Clearly differentiates from sibling tools (get_catalog, get_product) which are read-only queries.

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?

States explicit use cases: 'what you looked for and did not find' or 'introduce yourself.' Implicitly distinguishes from siblings, but does not explicitly list when not to use or name alternatives.

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