razz-mcp

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

With no annotations, description carries full burden. It successfully discloses the pagination/cursor behavior (serverTime/since loop) and hints at response contents (placement, scores). Missing: read-only safety confirmation, rate limits, or ordering guarantees.

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?

Four sentences, zero waste. Front-loaded with core purpose, followed by return value details, parameter usage pattern, and response handling. Every clause provides distinct information.

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 2-parameter read operation. Compensates for missing output schema by enumerating return fields (placement, scores, match details, serverTime). Could improve by noting default limit behavior, though schema covers this.

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?

Despite 100% schema coverage (baseline 3), description adds significant semantic value by explaining the 'since' parameter's purpose in a polling workflow ('last check', 'next since value'), enriching the raw timestamp definition.

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 ('Get') and resource ('HexWar match results') with specific scope ('your recent'). Implicitly distinguishes from siblings like razz_get_match_history by specifying 'HexWar', but does not explicitly contrast with similar result-fetching tools.

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?

Provides clear polling pattern guidance ('Use since timestamp to only get new results since last check' and 'serverTime to use as your next since value'). Lacks explicit 'when not to use' or alternative recommendations (e.g., vs razz_get_hexwar_state).

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