purge-endpoint-queue

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

Discloses that only queued jobs are affected, in-progress continue running. Annotations indicate write operation (readOnlyHint=false) and idempotency (idempotentHint=true), which description aligns with. No contradictions.

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, no wasted words. Front-loaded with action and effect. Every sentence adds value.

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 simple tool with one parameter, no output schema, description covers purpose, scope, and use case completely. No gaps.

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 coverage is 100% with endpointId description. The description does not need to add much beyond 'ID of the Serverless endpoint'. Baseline 3 is appropriate as schema already conveys meaning.

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 clearly states the tool removes pending jobs from a Serverless endpoint queue, distinguishing between queued and in-progress jobs. It uses specific verbs ('Remove') and resource ('pending jobs from Serverless endpoint queue'). Differentiates from siblings that might delete or update endpoints.

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?

Explicitly mentions use cases: error recovery or clearing outdated requests. Lacks explicit when-not-to-use or alternatives, but context is clear enough for an agent to decide.

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