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

Annotations cover safety profile (readOnly/idempotent). Description adds crucial behavioral context: specific status enum values, polling frequency recommendation, cost ('Free'), and workflow transition logic not present in structured fields.

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 dense sentences with zero waste. Front-loaded with purpose, followed by return values, workflow transition, polling guidance, parameter source, and cost. Logical progression.

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?

Comprehensive for an async status tool. Covers lifecycle (pending→completed), polling mechanics, result retrieval handoff, and input provenance. Presence of output schema means detailed return structure doesn't need expansion.

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 (baseline 3). Description augments task_id semantics by enumerating specific async start tools that generate valid IDs (atlas_start_gem_analysis, etc.), helping the agent understand valid parameter sources.

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?

Clear specific verb ('Check') and resource ('status of any async task'). Explicitly distinguishes from sibling 'careerproof_task_result' by stating when to use each (status vs. full results).

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 workflow guidance: use for polling, then switch to careerproof_task_result when 'completed'. Lists prerequisite task sources (atlas_start_* tools). Includes operational polling interval (5-10 seconds).

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