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

With no annotations provided, the description fully discloses behavior: it is free, reads data, returns aggregates and per-subject rows with badge URLs, and explains the reliability metrics measured (availability, contract stability, latency, TLS). No destructive actions are implied, and the 'measured|partially-measured|unmeasured' labeling adds transparency.

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 verbose and includes marketing language (e.g., 'The fast way to see who is actually reliable before you depend on them') that doesn't add essential functional information. While detailed, it could be significantly shorter without losing clarity.

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?

Despite lacking an output schema, the description thoroughly explains the return structure: ecosystem aggregates (counts, failures, drifting, median p95) and per-subject rows with badge URLs. This fully equips the agent to understand the output, given the tool's single optional parameter.

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 single parameter 'limit' is fully described in the input schema with min, max, and description. Schema coverage is 100%, so the description adds no additional meaning beyond what the schema provides, warranting the baseline of 3.

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 identifies the tool as reading a live reliability scoreboard, specifying the verb 'Read' and the resource 'aicomglobal's Live Reliability Scoreboard'. It distinguishes from sibling tools like aicom_verdict by positioning itself as the free top-of-funnel to those services.

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 checking reliability before depending on services but does not explicitly state when not to use this tool or compare it with alternatives. It mentions it's free and a top-of-funnel, but lacks direct exclusions or sibling comparisons.

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