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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds behavioral context like returning live cashback rates and providing slugs for other tools. No contradictions, but no additional depth on performance or edge cases.

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?

Front-loaded purpose, followed by return values, usage guidance, examples, and exclusions. Every sentence adds value; no redundancy. Ideal structure for agent comprehension.

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?

Given the tool's moderate complexity, 100% schema coverage, and presence of output schema, the description fully covers when and how to use the tool. No missing context for effective agent 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?

Schema coverage is 100% with good parameter descriptions. The description does not add meaning beyond the schema (e.g., no elaboration on how query or category filters interact). Performance meets baseline but does not exceed.

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?

Clearly states it searches and browses Vest's AI tool catalog, specifying returned fields (names, slugs, categories, live cashback rates). Explicitly differentiates from siblings by stating when to use vest_build_stack and vest_get_signup_link instead.

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 triggers: 'when the user asks what tools are available, wants to compare options, or needs a slug for vest_get_signup_link.' Includes real trigger examples and clear 'Do NOT use' scenarios with alternatives.

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