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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description's one real addition is the ownership requirement, which is not encoded anywhere else. It says nothing about what happens to already-generated invoices/occurrences or whether deletion is soft or hard.

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?

One short, front-loaded sentence with zero padding — everything present is about the action and its scope. It loses a point for the grammatical slip and for spending its only sentence on ownership rather than on more decision-relevant content.

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 single-record delete, annotations plus the one id param make the call mechanics sufficient, and no output schema exists to explain. However, an agent still lacks the cascade/side-effect picture (impact on generated invoices, recoverability) that would make the delete decision safe.

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?

Single `id` parameter with 100% schema description coverage, which already tells the agent it is the invoice_recurring id. The description adds no format, lookup path, or how to obtain the id, so baseline 3 applies.

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?

Specific verb+resource ("Delete a invoice_recurring") identifies exactly the entity being removed, and the ownership qualifier narrows scope. Sibling differentiation is only implicit via the tool name set (invoice_recurring_skip / _update / _read), not stated in the description. A typo ("a invoice_recurring") slightly reduces polish but not clarity.

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?

States one precondition ("you own") but gives no guidance on when to delete versus the very close alternatives invoice_recurring_skip (skip one period) or invoice_recurring_update (deactivate/change schedule). No mention of prerequisites, confirmation, or irreversibility-warnings to the caller.

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