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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it never explains what a submission overwrites, whether resubmission replaces prior ratings, how the idempotency_key behaves, or what permissions are needed for a destructive write.

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?

A single front-loaded sentence with no filler, which is structurally clean. However, brevity here comes at the cost of substance rather than from disciplined editing, so it is minimally adequate rather than exemplary.

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?

This is a destructive, idempotent mutation with a nested ratings array, six parameters, and no output schema or schema descriptions. The description should at minimum explain the ratings payload shape and idempotency/resubmission semantics; it covers neither, leaving an agent under-informed before a write.

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 burden. It only gestures at 'explicit ratings' while saying nothing about interview_session_id, interviewer_user_id, overall_notes, request_id, or idempotency_key, nor about the rating scale (0-4) or valid item_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 names a specific verb and resource: submitting an interview-session scorecard, with the qualifier that ratings must be explicit. An agent can identify the action unambiguously. It does not, however, distinguish this from nearby siblings such as yardstick_interview_sessions_complete or yardstick_final_recommendation_record.

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?

There is no guidance on when to use this tool versus alternatives, nor prerequisites such as whether the interview session must be completed or the interviewer assigned before submitting. The phrase 'with explicit ratings' hints at required content but is not a usage condition.

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