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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only the content scope (which policy domains the read returns). It says nothing about caching, freshness, or whether the policy can change between calls — which matters for a rules-of-record tool an agent may rely on before acting.

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 with the action and content scope front-loaded and the cross-references trailing. Every clause carries distinct information: the verb, the resource, four covered topics, and two sibling pointers. Nothing is redundant.

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?

An output schema exists, so return structure needn't be described, and with zero parameters there is no input burden to discharge. The description covers what the tool returns topically and which siblings to consult. The one missing piece is when an agent should call it — e.g. before any consequential action — which would sharpen its role among the gate-related siblings.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema is closed (additionalProperties: false) with an empty example, consistent with the description's implied no-argument call.

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?

Specific verb ('Read') plus a named resource ('Burs-IA rules') with the covered topics enumerated: autonomy, human oversight, revocation, and consequential-action gates. It also points at related siblings (outbound_gateway_policy, bursia_status), so an agent can place it in the family. It stops short of 5 because it never states what distinguishes this policy read from those siblings beyond the topic list.

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 'see outbound_gateway_policy, bursia_status' clause signals related tools but frames them as further reading rather than as alternatives with selection criteria. There is no explicit 'use this when...' or 'do not use this for...' guidance. Usage is inferable from the topic list, which is the definition of implied-only guidance.

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