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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds two genuinely useful behavioral facts not in annotations: routing incurs no model call, and the payload includes this week's decisions plus match frequency. It stops short of stating the reporting window precisely, pagination, or volume of returned rules, and with no output schema those gaps remain.

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?

Two sentences, zero filler, and the core purpose is front-loaded before the secondary cost note. Nothing could be removed without losing information.

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 simple read-only, single-parameter tool the description covers what comes back (rules, weekly decisions, match counts) and the no-model-call cost. Missing pieces are the meaning of the required company UUID and any routing hint versus the history/test/update siblings, which an agent would need before calling with confidence.

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 required parameter 'company' is a UUID with 0% schema description coverage, and the description never mentions it at all — not whether it is the acting company, the tenant whose rules are read, or the current session's organization. With coverage below 50%, the description is expected to compensate and does not.

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 (the routing rules Summer applies before any agent runs), and adds substantive scope: plain-language rules, this week's decisions, and per-rule match counts. It distinguishes itself implicitly from summer_router_rules_update, _test, and _history by verb, but never names those siblings or states the contrast explicitly.

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?

There is no explicit when-to-use guidance or exclusion relative to the sibling tools summer_router_rules_history (past rules), summer_router_rules_test (dry-run), or summer_router_rules_update. Usage is only implied: an agent wanting to inspect current rules and recent routing outcomes would pick this, but that inference is left entirely to the agent.

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