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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so 'Read only' is redundant. The description adds genuine behavioral context by noting that the result may include account-wide guardrails applied by a white-label partner, meaning the returned set isn't strictly site-owned.

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 short sentences with zero filler; the resource definition is front-loaded and the routing hint follows. Every clause earns its place.

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 one-parameter read tool whose annotations already declare the safety profile, this is nearly complete. The only modest gap is that no output schema exists and the description doesn't describe the shape of the returned guardrail entries, though it does hint at their scope.

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 a single required 'site' parameter with 100% schema description coverage (including the allowed value), so the schema carries the full burden. The description adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 resource (content guardrails/writing rules attached to this site) and scope, and clarifies that account-wide partner-applied rules are included. An agent can distinguish this from list_guardrails (the library) without opening either schema.

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?

Explicitly routes library-management tasks to list_guardrails / create_guardrail, which is clear when-to-use guidance. It doesn't address the sibling update_site_guardrails or state exclusions for this read, so it falls just short of a full when/when-not treatment.

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