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

Annotations declare readOnlyHint=true, yet the description explicitly says 'Create a draft-only application or opportunity packet,' which describes a creation/write action. This directly contradicts the read-only annotation, so the score is 1 even though the description adds useful draft/approval context.

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?

Two sentences, front-loaded with the core action, and the second sentence adds the critical human-approval constraint. There is no filler or repetition of what the schema or annotations already provide.

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?

For a tool with six parameters and zero schema descriptions, the definition is incomplete: it omits parameter semantics and any explicit routing guidance among the many talent_scout sibling tools. The output schema covers return values, but an agent cannot confidently populate all inputs from this description alone.

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 description coverage is 0%, and the description only implies queue_item_id via 'existing Talent Scout queue item.' The meanings of actor_id, tenant_id, output_kind, opportunity_mode, and notes are left unexplained, so the description does not compensate for the uncovered schema.

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 ('Create') with a specific resource ('draft-only application or opportunity packet') and a clear source ('existing Talent Scout queue item'). This distinguishes it from sibling tools like talent_scout_record_application or talent_scout_compose_application.

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?

The description clearly indicates the input condition: an existing Talent Scout queue item, and the draft/approval constraint signals this is for pre-approval packet generation. It does not explicitly name alternative tools or exclusions, so it stops short of a 5.

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