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

Description adds 'Irreversível' (irreversible) beyond the destructiveHint=true annotation, and notes bulk execution support. No contradictions with annotations.

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 concise sentences with key info front-loaded: operation, requirement, irreversibility, bulk support. No extraneous text.

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?

Covers essential aspects for a simple destructive tool: purpose, required param, irreversibility, bulk. Missing details like return value or impact on subscriptions, but acceptable given simplicity and no output schema.

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?

Description explains plan_id as required and plan_ids for bulk execution (2 of 3 params), but does not mention the 'account' parameter. With 0% schema coverage, the description partially compensates.

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?

Description clearly states 'Remove um plano' (delete a plan), specifies the API version (V5), and distinguishes from sibling tools like create, update, get, and list. The verb 'remove' and resource 'plano' are unambiguous.

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?

Description mentions required plan_id and bulk support with plan_ids, but does not explicitly state when to use this tool versus alternatives (e.g., updating a plan instead). Usage is implied but no direct guidance.

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