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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile needs no restating. The description's added value is the defaulting semantic — that this is the ruleset governance calls fall back to — which is genuinely useful, but nothing is said about the returned object or any access/tier constraints beyond the 'PRO' marker.

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 sentence, front-loaded with the verb and resource, with the qualifying clause placed immediately after. No filler.

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 getter with annotations covering safety and a fully documented single parameter, the description supplies enough to call it correctly. The shape of the returned ruleset is left unstated (no output schema), which is the only notable gap.

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 optional `context` parameter with 100% schema description coverage that already explains its purpose and that it is never used to rank or included in the answer. The description adds no parameter meaning beyond that, so the schema-derived baseline of 3 applies.

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?

States a specific verb and resource ('Read your org default ruleset') and defines what that resource is: the fallback used by governance calls without an explicit `ruleset`. It does not explicitly contrast with the many ruleset siblings (set_org_ruleset, describe_rule, validate_ruleset), so it stops short of the top score.

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 defaulting clause implies when this matters — when a governance call has no `ruleset` of its own — but there is no explicit 'use this instead of X when Y' guidance and no exclusions relative to describe_rule, document_ruleset, or validate_ruleset.

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