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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint, so the risk profile is covered. The description adds genuinely useful non-annotation context: 'No PIN required, matching chat,' which clarifies the authentication expectation for this destructive call.

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?

Three sentences, fully front-loaded with the action and scope, then the prerequisite, then the parameter decision tree. No filler and every sentence carries operational information.

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, no-required-param tool with no output schema, the description covers the prerequisite, auth note, and parameter precedence well. It could state what the caller receives on success (e.g., cancelled count or ids), but annotations otherwise carry the safety profile.

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 100%, so the baseline is 3, but the description adds real semantics beyond the schema: the mutual-exclusion precedence ('provider ignored if id is also given') and the omit-both default that cancels ALL schedules, which the schema does not state.

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?

States a specific verb+resource ('Cancel ... schedules') and precisely scopes it (one, per-provider, or all) for the linked wallet, distinguishing it from sibling list_schedules and schedule_bill.

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?

Explicitly instructs to call list_schedules first to obtain a real id, and gives clear selection rules for each parameter combination including the omit-both case. Alternatives and precedence are spelled out, leaving nothing to inference.

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