Favro MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Move a column') and return value ('updated column details'), but fails to mention critical behavioral aspects like required permissions, whether the move affects other columns' positions, error conditions, or mutation implications. The description is minimal and lacks necessary operational context.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured but slightly verbose; every sentence adds value, though the formatting could be more streamlined for an AI agent.

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 3 parameters), no annotations, and an output schema (which covers return values), the description is moderately complete. It explains the action and parameters but lacks behavioral context like permissions or side effects, making it adequate but with clear gaps for safe and effective use.

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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It clarifies that 'column' can be an ID or name, 'position' is 0-based, and 'board' is required for name lookup—details not present in the schema. However, it doesn't fully explain all three parameters' purposes or interactions, leaving some gaps.

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 ('Move a column') and the target resource ('to a new position'), distinguishing it from sibling tools like 'create_column', 'rename_column', and 'delete_column'. The verb 'move' precisely indicates repositioning rather than creation, modification, or 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 implies usage for repositioning columns, but provides no explicit guidance on when to use this tool versus alternatives like 'create_column' or 'rename_column'. It mentions the 'board' parameter is required for name lookup, which offers some contextual hint, but lacks clear when/when-not instructions or sibling tool comparisons.

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