Favro MCP

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It states this is a creation operation (implying mutation) and mentions default behaviors (uses current board if not specified, appends to end if position not specified), but lacks critical details like permission requirements, whether the operation is idempotent, error conditions, or rate limits.

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 efficiently structured with a clear purpose statement followed by parameter explanations in a bullet-like format. Every sentence adds value: the first states the action, and the subsequent lines clarify each parameter's role and default behavior without redundancy.

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 moderate complexity (3 parameters, mutation operation), no annotations, and an output schema exists (so return values are documented elsewhere), the description is partially complete. It covers parameters well but lacks behavioral context like permissions, side effects, or error handling, which are important for a creation tool.

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 significant value beyond the 0% schema description coverage by explaining all three parameters: 'name' as column name, 'board' as board ID or name with default behavior, and 'position' as 0-based index with default behavior. This fully compensates for the schema's lack of descriptions, though it doesn't provide format examples or constraints.

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 action ('Create a new column') and resource ('on a board'), making the purpose immediately understandable. It distinguishes from siblings like 'rename_column' or 'delete_column' by specifying creation. However, it doesn't explicitly differentiate from 'move_column' which also involves column positioning.

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. It doesn't mention prerequisites (e.g., needing board access), when not to use it, or how it relates to sibling tools like 'rename_column' or 'move_column'. The only implied context is that a board must exist.

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