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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: a conditional requirement (a note is mandatory for recruiter questions) and an external side effect (send_to_recruiter shares a scorecard note with the recruiter). It still does not say what the destructive action finalizes or whether it is reversible, so it is a moderate rather than rich disclosure.

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 tight sentences with no waste; the core action leads and the conditional/side-effect rules follow. Compact and front-loaded, though the second sentence packs two distinct rules into one clause chain.

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 destructive, non-idempotent mutation with six parameters at 0% schema coverage and no output schema, the description leaves too much unspecified: the meaning of the decision enum, what a successful response looks like, and how request_id/idempotency_key should be used. It is not sufficient for an agent to invoke this confidently.

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% across six parameters, so the description carries the full burden. It explains only two of them ('note' conditionally, 'send_to_recruiter') and never maps any of the six enum values for 'decision' (approve/reject/hold/ask_recruiter/thumbs_up/thumbs_down) or clarifies task_id, request_id, or idempotency_key.

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 a specific verb and resource ('Answer an assigned application or scorecard review'), which is clearly distinct from the read-only siblings yardstick_tasks_list and yardstick_tasks_deep_link. It does not name those siblings explicitly, but the action/read distinction is obvious from the verb.

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?

Usage is implied by 'assigned ... review task' and one conditional rule is given ('Recruiter questions require a note'), but there is no guidance on when this tool is the right choice versus alternatives, and no prerequisites or exclusions are stated.

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