deleteTransfer

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

With no annotations and no behavioral details, the description falls entirely short. It does not disclose that deletion is irreversible, whether cascading effects occur, authentication requirements, or what happens if the transfer does not exist.

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 short phrase, but this is under-specification rather than effective conciseness. It omits essential context that would make the description useful, so the brevity is not earned.

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 the simple one-parameter schema, a delete operation requires clarity on irreversibility, authorization, and error behavior. The presence of an output schema does not compensate for the complete absence of behavioral context, so the description is not complete enough for an AI to use the tool confidently.

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?

The input schema defines a single 'id' integer with no description, and the tool description adds no parameter information. The parameter's role is inferable from the tool name, but with 0% schema description coverage, the description should explicitly identify 'id' as the transfer ID to delete.

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 'Excluir transferência' translates to 'Delete transfer,' which is a direct translation of the tool name itself. It states the action and resource but adds no new information beyond the name, making it effectively tautological.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives like deleteTransaction or deleteAccount, nor does it state any prerequisites or conditions.

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