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

Strong: Annotations declare read-only/idempotent/safe properties. Description adds critical behavioral context not in annotations: state requirement (must be completed), cost ('Free'), and return structure ('scores, competency breakdown, and recommendations'). Does not contradict 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?

Perfect efficiency: Four sentences covering (1) core action, (2) return payload, (3) parameter source, (4) prerequisites/cost. Zero waste, front-loaded with the essential verb, every clause adds distinct 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?

Complete for tool complexity: Single-parameter read-only tool with no output schema. Description compensates for missing output schema by detailing return contents (scores, breakdowns, recommendations) and covers workflow prerequisites comprehensively.

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?

Exceeds baseline: With 100% schema coverage, baseline is 3. Description adds valuable provenance context specifying analysis_id originates from 'atlas_start_gem_analysis response or atlas_list_analyses', helping the agent understand the data flow beyond the schema's type 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?

Excellent: Specific verb 'Retrieve' + resource 'completed analysis result' + key 'by analysis ID'. Clearly distinguishes from sibling 'atlas_start_gem_analysis' (which creates) and 'careerproof_task_status' (which checks completion) by stating it fetches results and requires completion first.

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?

Outstanding: Explicitly states prerequisite 'check with careerproof_task_status first' and condition 'Only works after analysis is completed'. Identifies exact sibling tools that produce the required ID (atlas_start_gem_analysis, atlas_list_analyses). Includes cost signal 'Free'.

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