Rekko MCP

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

No annotations provided, so description carries full burden. Mentions applicability to both 'running or completed' states, implying it's safe to call repeatedly. However, lacks disclosure of polling patterns, typical latency, rate limits, or cache behavior expected for status-checking tools.

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?

Front-loaded purpose statement followed by Args documentation. Efficient with no wasted words, though the Args format is slightly redundant with the schema structure (necessary given 0% schema coverage).

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?

Adequate for a single-parameter status tool with output schema. Covers core workflow relationship to analyze_market. Gap: should mention typical async polling pattern since it explicitly handles 'running' analyses, and possible status values returned.

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 coverage is 0% (no property descriptions), but the description compensates effectively by documenting the parameter inline: 'Analysis identifier returned by analyze_market.' This provides both semantic meaning (ID type) and provenance (source tool), though format constraints could be added.

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?

Clear verb ('Check') + specific resource ('status of a running or completed analysis'). The focus on 'status' effectively distinguishes this from sibling 'analyze_market' (which initiates) and 'get_analysis' (which likely retrieves results data).

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?

Establishes clear workflow context by stating the analysis_id is 'returned by analyze_market', indicating when to use the tool. However, lacks explicit guidance on when to prefer this over 'get_analysis' or polling best practices for long-running analyses.

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