Favro MCP

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

With no annotations provided, the description carries full burden and does well by disclosing pagination behavior ('0-indexed, default 0', 'up to 100 cards'), return format ('list of cards with pagination metadata'), and optional filtering ('column to filter by'). It doesn't mention rate limits or auth needs, but covers core operational traits.

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 organized sections for Args and Returns. Every sentence adds value with no redundancy, making it efficient and well-structured.

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 (list operation with filtering/pagination), no annotations, and an output schema present (so return values are documented elsewhere), the description is complete enough. It covers purpose, parameters, behavior, and output at an appropriate level.

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 meaning for all 3 parameters: 'board' accepts multiple identifiers, 'column' is optional for filtering, and 'page' specifies indexing and default. This provides clear semantics beyond the bare schema.

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 ('List cards') on a specific resource ('on a specific board') with a key feature ('with pagination'). It distinguishes from siblings like 'get_card_details' (detailed view) and 'list_boards' (different resource).

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 listing cards on boards, but doesn't explicitly state when to use this versus alternatives like 'get_card_details' for detailed info or 'list_columns' for board structure. No guidance on prerequisites or exclusions is provided.

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