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

Annotations declare read-only/idempotent status. Description adds valuable behavioral context: cost ('Free'), workflow sequencing (prerequisite for analysis tools), and specific data payload details not covered in annotations.

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?

Four efficient sentences with zero waste: purpose → parameter source → usage guideline → cost. Front-loaded with most critical information. No redundancy with schema or annotations.

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?

Complete for a retrieval tool with output schema present. Description wisely summarizes return value categories without repeating full schema, covers prerequisites, cost, and workflow positioning adequately.

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 has 100% coverage, establishing baseline 3. Description adds semantic provenance ('from ceevee_upload_cv or ceevee_list_versions') that helps agent understand parameter sourcing beyond raw schema definition.

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?

States specific verb ('Get') + resource ('CV version') + detailed scope ('structured content, sections, word count, and audience profile'). Clearly distinguishes from sibling analysis tools by contrasting inspection vs. analysis functions.

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?

Explicit sequencing guidance ('Use to inspect CV content before running analysis tools') and prerequisite sourcing ('cv_version_id from ceevee_upload_cv or ceevee_list_versions'). Clear when-to-use vs. alternatives.

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