Favro MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but doesn't specify whether it requires authentication, has rate limits, or what happens if the board_id is invalid (e.g., error handling). For a tool with no annotations, this is a significant gap in transparency about its operational behavior.

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: the first sentence clearly states the purpose, followed by structured 'Args' and 'Returns' sections. There's no wasted text, and each part adds value. However, the structure could be slightly improved by integrating the parameter explanation more seamlessly, but it remains efficient and well-organized.

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 low complexity (one parameter) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose, parameter semantics, and return overview. However, it lacks usage guidelines and behavioral details, which are minor gaps given the simple nature of the tool. For a basic retrieval tool, this is nearly sufficient.

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 schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'board_id' is 'The board's widget_common_id,' which clarifies the parameter's purpose beyond the schema's basic type. However, it doesn't provide examples, format details, or constraints (e.g., length, valid values), leaving some ambiguity. With one parameter and partial compensation, a baseline 3 is appropriate.

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 tool's purpose: 'Get details of a specific board including its columns.' It specifies the verb ('Get') and resource ('board'), and distinguishes it from siblings like 'list_boards' (which lists multiple boards) and 'get_current_board' (which gets the current board without an ID). However, it doesn't explicitly contrast with 'get_card_details' or other detail-retrieval tools, keeping it from a perfect score.

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 when to choose 'get_board' over 'get_current_board' (e.g., for a specific vs. current board) or 'list_boards' (e.g., for details vs. a list). There's also no mention of prerequisites, such as needing a board ID from 'list_boards' first. This lack of contextual guidance limits its utility for an AI agent.

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