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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that entries carry the actor and stated reason; it says nothing about ordering, completeness of history, retention, or volume, which the annotations do not cover.

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?

A single front-loaded sentence with no filler or hedging. It is essentially a verbatim restatement of the title, so it is efficient but contributes no additional information beyond that line.

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 read-only history tool with no output schema and a bare one-parameter schema, the description says enough to know what the call returns conceptually (revisions plus author and reason) but not enough to call it confidently: no pagination, ordering, or certainty of what the company UUID refers to.

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 is one required parameter, company, whose schema has 0% description coverage – the schema only gives type uuid plus a pattern, with no statement of what the company scopes. The description never mentions the parameter, so an agent must guess whether the company is the tenant whose router rules are being audited.

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 names a specific verb ("Read") and resource ("saved revisions of the router rules") and states the payload includes author and reason, which separates it in spirit from summer_router_rules_read (current state) and summer_router_rules_update. Sibling differentiation is only implicit, since no other tool is named.

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?

Usage is implied: an agent can infer this is the audit/history counterpart to summer_router_rules_read. There is no explicit "use this when you need past revisions, not current rules" statement, no note on when the history would be empty, and no mention of the sibling alternatives.

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