delete_board

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It states the board is deleted and that a confirmation response is returned, but it does not mention permanence, cascading deletion of lists/cards, or required permissions, all of which are material for a destructive tool.

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 compact and front-loaded: one clear opening sentence, then a minimal Args/Returns structure. Every element earns its place with no fluff or repetition of the schema.

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 one-parameter delete operation with an output schema, the invocation requirements are adequately covered (id and a confirmation return). However, the absence of deletion-impact context such as irreversibility or what happens to contained cards/lists leaves the definition incomplete for a destructive tool with no annotations.

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 0%, so the description must document the single parameter; it does so by explaining that 'id' is 'The Trello board ID to delete.' This adds real meaning beyond the bare title 'Id' in the schema. A 4 is appropriate because the explanation is correct and sufficient, though terse.

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 a specific verb-resource pair ('Delete a Trello board'), so an agent can tell this is a destructive board-level operation rather than a card/list operation. It does not add any qualifiers or side-effect scope to further differentiate from sibling tools, so it stops short of a 5.

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 guidance is provided about when to use this tool versus alternatives such as delete_card or create_board, and no conditions, prerequisites, or exclusions are stated. The agent must infer the tool's role entirely from its name and the one-line description.

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