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

Annotations already declare readOnlyHint=true, lowering the burden. The description adds meaningful behavior context: data comes from an hourly signed snapshot, recovery counts use a 30-day window, and deterministic vs agentic recovery are clarified. The final 'available=false when unavailable' line is somewhat tautological but still indicates a response behavior.

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 front-loaded with the main action, but the rest is one dense sentence with nested parentheticals and a long list of metrics. The final 'available=false when unavailable' sentence is redundant and does not earn its place, making the structure harder to parse than necessary.

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?

For a parameterless, read-only tool with no output schema, the description is largely complete: it names the major metrics, the time window, and the data source. Minor ambiguity remains about the response shape and the exact semantics of 'available', but an agent can invoke the tool correctly without more information.

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?

There are zero parameters and schema coverage is trivially 100%, so the baseline is 4. The description compensates by defining domain-specific terms and data partitions, though there are no actual parameters to document.

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 identifies a specific resource ('FlareWatch agent's reliability scorecard') and opens with a concrete verb ('Return'), then enumerates the metrics included. It does not explicitly differentiate itself from sibling tools like get_agent_capabilities or get_recent_agent_actions, so it stops short of maximum clarity.

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 gives no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent would have to infer from the name and metric list that this is the right tool for agent reliability status, but the description itself does not help choose between it and related agent tools.

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