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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely non-structured behavior: this is a soft delete scoped to the record only, it is reversible for 30 days via restore_deleted, and it has no real-world account impact. That is exactly the extra context an agent needs before committing a 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?

Front-loaded with the core action, then alternatives, recovery, and id sourcing in a logical order. The closing disclaimer about estimates and non-advice is boilerplate that does not help an agent select or invoke a delete tool, so it dilutes an otherwise tight definition.

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 single-parameter destructive tool with no output schema, the description covers everything needed: what is deleted, what is not affected, how to avoid deletion, how to undo it, and how to get the identifier. No gap remains that would cause a misinvocation.

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 description coverage is 0%, but there is only one parameter (a UUID 'id'), which sets a high baseline. The description compensates usefully by telling the agent to obtain the id from beyondpayday_list_assets, which the schema's format/pattern does not convey. It does not explain the sentinel UUID values permitted by the pattern, a minor remaining gap.

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 and resource ('Deletes an asset record') and immediately scopes it against the real-world object ('does not close any real account'). It also distinguishes itself from the near-sibling beyondpayday_update_asset, so an agent can separate delete from disable without opening either schema.

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?

Gives an explicit when-not plus the alternative: 'To keep the asset but leave it out of totals, set enabled: false with beyondpayday_update_asset instead.' It also names the recovery path (beyondpayday_restore_deleted, 30-day window) and where to source the id (beyondpayday_list_assets). Nothing about tool selection is left to inference.

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