ynab_get_payee

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. Description adds value by detailing the return structure (id, name, transfer_account_id, deleted, cached, cache_info) and error conditions. No contradictions.

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?

Structured into clear sections (Args, Returns, Errors) with no unnecessary words. Front-loaded with purpose, then concise parameter and error details. Every sentence is informative.

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 retrieval tool, the description covers all necessary aspects: parameter behavior, return format, caching info, and error handling. The presence of an output schema (not shown) further supplements completeness.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: budget_id (optional, omit for default), payee_id (required), response_format (json/markdown, default markdown). Adds meaning beyond schema types.

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 'Get details for a specific payee', which is a clear verb+resource combination. It naturally distinguishes from sibling 'ynab_list_payees' which retrieves all payees, not a single one.

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?

Provides explicit error guidance ('No default budget set' → run ynab_set_default_budget first) and clarifies optional parameter usage. Does not explicitly state when to use this tool instead of alternatives, but the error handling and parameter hints imply proper usage.

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