get_publish_approval

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

No annotations provided, so description carries full burden. Explains that 'readiness' is recomputed on read, and defines fields like 'readinessAtRequest' and 'readinessChanged'. Mentions checking for 'dry_run_required' blocker. Good behavioral context, though could note idempotency.

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?

Three sentences, front-loaded with main purpose. No filler. Could be slightly more structured, but very efficient.

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?

Given one parameter, no output schema, and no annotations, description covers purpose, usage context, behavioral details, and parameter source. Adequately complete for a read tool.

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?

Only parameter 'approvalId' is described with context: 'from request_publish_* or list_publish_approvals'. Schema coverage is 100%, but description adds where to get the ID, adding value beyond 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?

Description states 'Read one publish approval by id' with specific verb and resource. It distinguishes from 'list_publish_approvals' by explaining it lets you poll a specific request instead of re-fetching the whole list.

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?

Clear context: 'poll a specific request rather than re-fetching the whole list' indicates when to use. Also mentions checking if a blocker has been cleared. No explicit when-not or alternatives beyond list, but sufficient.

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