remove_my_tool

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

It discloses a concrete effect: 'HyperRoute stops routing to it immediately and goes back to ranking catalog tools for that region.' This goes beyond a basic removal statement, though it does not mention reversibility or other potential side effects.

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 two sentences with no redundant wording. It efficiently conveys the action and its immediate effect, fitting within a compact scope.

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?

With no output schema and a single simple parameter, the description provides sufficient context for the core operation. It does not explain error conditions or return values, but these are not critical for a basic removal action.

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?

The only parameter 'tool_id' is not described beyond the schema's type and title. The description does not explain its meaning or format, relying on context from the tool name and purpose. It is simple but not fully elaborated.

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 action: 'Remove one of the user's declared tools.' It uses a specific verb and resource, and the additional context about routing behavior reinforces the purpose without ambiguity.

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?

The description implies the tool is for removing declared tools but does not explicitly compare with alternatives like 'unprefer_tool' or 'update_my_tool.' It lacks explicit guidance on when to use this tool over others.

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