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 mentions the action ('Assign or unassign') but fails to specify permissions required, whether changes are reversible, rate limits, or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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 well-structured and appropriately sized, with a clear purpose statement followed by parameter explanations and return info. Every sentence adds value, though the 'Args' and 'Returns' sections are slightly redundant with the schema but still informative given low coverage.

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 complexity (mutation with 4 params), no annotations, and an output schema present, the description is moderately complete. It covers parameters well but lacks behavioral context and usage guidelines. The output schema reduces the need to explain returns, but more guidance on when and how to use the tool would improve 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 effectively explains the semantics of all four parameters: 'card' (ID, sequential ID, or name), 'user' (ID, name, or email), 'board' (needed for name lookups), and 'remove' (to unassign). This adds crucial meaning beyond the bare schema, though it could detail format constraints further.

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 ('Assign or unassign a user from a card') with the resource ('card'), distinguishing it from siblings like 'update_card' or 'tag_card' which modify different aspects of a 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 provides no guidance on when to use this tool versus alternatives like 'update_card' or 'tag_card', nor does it mention prerequisites or exclusions. It lacks context about when assignment/unassignment is appropriate, leaving usage decisions to inference.

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