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. It discloses the dual behavior (add/remove) and mentions that board is needed for name lookups, which adds context. However, it doesn't cover permissions, rate limits, or mutation effects beyond the basic operation, leaving gaps for a tool with write capabilities.

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 structured parameter explanations and return value. It's appropriately sized with no wasted sentences, though the Args/Returns formatting could be slightly more integrated for optimal flow.

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 4 parameters with 0% schema coverage, no annotations, but an output schema exists, the description does well: it explains the tool's purpose, parameter meanings, and notes the return. It compensates for the lack of schema descriptions, though more behavioral context (e.g., error cases) would enhance completeness.

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%, so the description must compensate. It adds meaningful semantics: card can be ID, sequential ID, or name; tag can be ID or name; board is needed for name lookups; remove toggles action. This clarifies beyond the schema's basic types, though it doesn't detail all parameter interactions or formats.

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 ('Add or remove a tag') on a specific resource ('from a card'), distinguishing it from siblings like assign_card, update_card, or move_card. It precisely defines the tool's function without being vague or 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?

The description implies usage through the 'remove' parameter, suggesting when to use for removal vs. addition, but lacks explicit guidance on when to choose this tool over alternatives like update_card for tag modifications or prerequisites. No sibling tool comparisons or exclusions are provided.

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