scraper_server_status

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

The description indicates a read-only operation ('Check', 'Shows') without explicit read-only flag, but no annotations exist. It does not mention any destructive side effects or required permissions, which is acceptable for a simple status check. The listed outputs provide adequate behavioral context.

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 only two sentences (about 20 words), directly stating the purpose and what is shown. No unnecessary words or repetition. It front-loads the key action and then provides specifics.

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 no parameters and no output schema, the description fully explains the tool's role and outputs. It covers server health, circuit breaker, failure counts, and times, which is complete for a status check tool.

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 no parameters, and the schema coverage is 100% (no undocumented parameters). The description does not add parameter-level detail because none are needed. Baseline score 4 for zero parameters.

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 checks the status of all ScraperServer instances, listing specific metrics (server health, circuit breaker state, failure counts, times). It is easily distinguished from siblings which deal with billing, usage, or scraping URLs.

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 for monitoring system health, with clear context. No explicit when-not-to-use or alternatives are provided, but the context is sufficient for an agent to infer when to use this tool.

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