MCPAmpel

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

No annotations provided, so description carries full burden. Mentions 'daily quota' and 'remaining scans' revealing rate-limiting domain model, but omits whether this consumes quota itself, output format/structure, or read-only safety 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?

Single sentence, seven words. Information-dense with zero redundancy. Front-loaded with action verb and specific resource targets.

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 zero-parameter status tool. Describes what information is returned (quota and remaining scans) despite lack of output schema. Could improve by indicating return structure or that results are real-time.

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?

Zero parameters present per schema. With no parameters to document, baseline score applies. Description appropriately focuses on behavior rather than inventing parameter semantics where none exist.

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?

Specific verb 'Show' paired with clear resources 'daily quota usage and remaining scans'. Distinctly differs from siblings (scan_url, scan_my_servers, get_scan_results) by focusing on account limits rather than performing or retrieving scans.

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?

Implies usage context (checking limits before scanning) through content but lacks explicit when-to-use guidance or warnings. Does not state 'use this before scan_my_servers to verify remaining quota' or clarify that it performs no scanning itself.

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