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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds non-obvious context the annotations cannot carry: the authorization requirement (workflow manager on an open job) and the behavioral meaning of the flag (the step gates candidate progression on the hiring manager's decision). It doesn't cover failure modes or whether existing/in-flight sessions are affected.

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 filler; the core effect is front-loaded and the permission caveat follows. Every sentence earns its place.

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 mutation tool whose annotations cover safety and idempotency, the description is adequate on effect and permissions, but with 5 parameters at 0% schema coverage and no output schema, the lack of any parameter-level detail (identifiers, idempotency key usage) leaves gaps an agent would need to guess at.

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 there are 5 parameters, so the description must compensate and mostly does not. It conveys the meaning of the key boolean 'hiring_manager_decides' but says nothing about interview_plan_id, step_id, request_id, or idempotency_key, leaving four undocumented parameters.

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 states a specific verb+resource: toggling whether a plan step waits on the hiring manager's decision. 'Turn on or off' plus 'plan step' plus the consequence ('before the candidate moves on') makes the effect unambiguous. It does not name or differentiate itself from the many interview_plans_* siblings, so it stops short of a 5.

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?

It supplies one real usage condition ('Only workflow managers on an open job can change it'), which tells the agent who may call it, but gives no routing guidance relative to alternatives such as modify_active_bind or publish_bind, and no statement of when this setting is relevant.

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