Favro MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively warns about the destructive nature ('This will also delete all cards in the column!'), clarifies the return value ('Confirmation of deletion'), and explains the board parameter's role for name lookup, covering critical behavioral traits beyond basic functionality.

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 front-loaded with the core purpose, followed by a critical warning, then structured sections for Args and Returns. Every sentence earns its place, with no wasted words, making it highly efficient and easy to parse.

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?

Given the tool's destructive complexity, no annotations, 0% schema coverage, but with an output schema (implied by 'Returns'), the description is complete. It covers purpose, behavioral risks, parameter semantics, and return confirmation, leaving no gaps for safe agent invocation.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'column' as 'Column ID or name' and 'board' as 'Board ID or name (required for name lookup)'. It adds essential meaning about how name lookup works, which the schema alone doesn't provide.

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 clearly states the specific action ('Delete a column from a board') with the resource identified, distinguishing it from siblings like delete_card, rename_column, or move_column. It's precise about what gets removed and the scope of the deletion.

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 clear context with the warning about deleting all cards in the column, which implicitly guides when to use this tool versus alternatives like delete_card for individual cards. However, it doesn't explicitly name alternatives or state when-not-to-use scenarios beyond the warning.

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