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

Adds substantial context beyond annotations: discloses 15-credit cost, 2-3 minute duration, exact polling limits (40 polls/20 min max), specific status values ('completed', 'failed'), and timeout behavior. Matches readOnlyHint: false with 'generate' write operation.

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?

Information-dense and well-structured with clear POLLING section and upfront cost/timing details. The enumeration of 17 report categories adds length but provides necessary discovery value given the lack of enums in the schema. No wasted sentences.

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 a complex async workflow with no output schema. Covers the full lifecycle (initiation → polling → download/error/timeout), credit costs, timing constraints, and enumerates all valid report categories to compensate for the open-ended string parameter.

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% so baseline is 3. Description adds valuable context by explaining that 'inputs' contains report-specific fields like role_title/industry and that cv_version_id enables 'CV-aware reports', plus the critical instruction to consult ceevee_list_report_types for valid report_type values.

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 uses a specific verb ('Generate') with clear resource ('CeeVee career-intel report') and explicitly distinguishes this from siblings by detailing the async workflow requiring subsequent calls to ceevee_get_report and ceevee_download_report.

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 prerequisites ('Call ceevee_list_report_types first'), step-by-step polling protocol ('every 30 seconds, up to 40 times'), and clear branching logic for completion/failure/timeout states with specific sibling tool names for each action.

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