clear_endpoints

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

No annotations are provided, so the description carries full burden. 'Remove all endpoints' suggests a destructive mutation, but it lacks details on permissions, reversibility, confirmation prompts, or effects on system state. It doesn't mention rate limits, error handling, or what 'remove' entails (e.g., deletion vs. deactivation).

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, direct sentence with no wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse.

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 destructive tool with no annotations and an output schema (which might cover return values), the description is insufficient. It doesn't explain behavioral traits like safety, side effects, or usage context, leaving critical gaps for an agent to understand when and how to invoke it safely.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, but this is acceptable given the empty schema, aligning with the baseline for zero parameters.

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 'Remove all endpoints' clearly states the action (remove) and target (endpoints), with 'all' specifying scope. It distinguishes from sibling 'remove_endpoint' (singular) but doesn't explicitly contrast with other siblings like 'list_endpoints' or 'add_endpoint'.

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 on when to use this tool versus alternatives like 'remove_endpoint' or 'list_endpoints'. The description implies a bulk operation but doesn't specify prerequisites, consequences, or recommend alternatives for partial removal.

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