application-cleanQueues

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

Despite annotations indicating idempotentHint and openWorldHint, the description adds no behavioral context beyond what annotations already provide. It fails to disclose side effects, prerequisites, or any operational details.

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?

While the description is short, it is underspecified rather than concise. It provides no substantive information, so it fails to earn its space.

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 the tool's parameter count, lack of output schema, and many sibling tools, the description is completely inadequate. It offers no meaningful context for an AI agent to select or invoke the tool correctly.

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 the description does not mention the required 'applicationId' parameter. No semantic meaning is added beyond the schema's structural definition.

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 is merely the HTTP path 'POST /application.cleanQueues', which restates the tool name without explaining its function. It does not specify what cleaning queues means or what resource is affected, making it a tautology.

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?

No guidance is provided on when to use this tool versus siblings like 'application-clearDeployments' or 'compose-cleanQueues'. The description offers no context for appropriate usage.

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