handle-duplicate-service

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

With no annotations, the description should disclose behavioral traits. It only says 'Handle user decision' and gives no details about side effects, permissions, or destructive potential. The action enum hints at possible mutations but is not explained.

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?

The description is a single short sentence, which is concise but under-specifies the tool. It could be expanded without losing efficiency, but the minimal length is not penalized heavily.

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?

The description is entirely inadequate given the tool's complexity (4 parameters, nested objects, no output schema). It fails to explain return values, error conditions, or workflow integration, leaving an agent with insufficient information to use 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 coverage is low (25%), but the description adds no parameter details. Key parameters like 'action' (enum) and 'options' (nested object) lack clarification on semantics or valid combinations, forcing the agent to infer from the schema alone.

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 'Handle user decision for duplicate service' is vague. It fails to specify what action the tool performs (e.g., creates, updates, deletes) or on what resource, making it unclear for an AI agent to distinguish its purpose.

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 'detect-existing-service' or 'deploy-service'. The description does not mention prerequisites or context, leaving the agent without usage boundaries.

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