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 tool returns board details or a message if none is selected, which is helpful. However, it doesn't disclose important behavioral aspects like whether this is a read-only operation (implied but not stated), what authentication is required, rate limits, or what format the 'message if none is selected' takes. For a tool with zero annotation coverage, this leaves significant gaps.

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 perfectly concise - two sentences that each earn their place. First sentence states the purpose, second sentence describes the return behavior. No wasted words, front-loaded with the core functionality.

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 this is a simple read operation with 0 parameters, an output schema exists, and the description covers the core purpose and return behavior, it's reasonably complete. The main gap is lack of behavioral context about authentication, rate limits, and the exact format of the 'none selected' message. However, for a straightforward getter tool, the description provides sufficient context for basic usage.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. It does mention the 'currently selected' context which helps understand the implicit input mechanism. Baseline for 0 parameters is 4.

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 the currently selected board.' This is a specific verb+resource combination that distinguishes it from siblings like 'get_board' (which likely requires board ID parameter) and 'list_boards' (which returns multiple boards). However, it doesn't explicitly contrast with 'get_board' in the description text itself.

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 context through 'currently selected board' - suggesting this tool should be used when working with a pre-selected board rather than specifying one. However, it doesn't explicitly state when to use this vs 'get_board' (which likely requires explicit board ID) or mention prerequisites like needing to first select a board using 'set_board'.

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