deleteCategory

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

With no annotations, the description carries the full disclosure burden. It discloses that replacement_id can move transactions, but it fails to state the default behavior when no replacement is provided — a critical safety concern for a destructive operation. Permissions, irreversibility, and impact on existing data are unmentioned.

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, succinct sentence with no filler. It front-loads the context ('Ao excluir') and delivers a specific, important behavioral detail. Every word earns its place.

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?

Despite having an output schema, this is a destructive operation with no annotations, and the description is far too minimal. It doesn't explain deletion consequences (e.g., what happens to transactions if replacement_id is omitted), prerequisites, or side effects. For a delete tool, this is incomplete.

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 50% (only replacement_id has a description). The description essentially duplicates the replacement_id semantics already in the schema ('mover as movimentações') without adding new information. The 'id' parameter has no description in either the schema or the tool description, leaving a 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?

The description uses the verb 'excluir' (delete) and hints at moving transactions via replacement_id, but it never explicitly names the resource (category). The purpose is vague without the tool name; it could apply to any deletable entity. It does distinguish sibling deletes by mentioning transaction migration, but the resource is not stated.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., deleteAccount, deleteCreditCard). It only explains an optional parameter behavior, not usage scenarios or prerequisites. No exclusions or alternative recommendations are given.

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