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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, covering the safety profile completely. The description adds nothing beyond that—no pagination behavior for limit/offset, no indication of ordering, and no note on what happens when a location has no assigned SOPs.

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 six-word sentence with zero waste, but it is under-specified rather than concise—one more clause about pagination or the sibling relationship would have cost little and added much.

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-value explanation is not required. Still, for a three-parameter paginated list tool with 0% schema description coverage, the description leaves the agent without the meaning of locationId or any guidance on limit/offset, which is a material 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?

Schema description coverage is 0%, so the description carries the burden for all three parameters and fails: locationId is only obliquely referenced as 'a site', while limit and offset are never mentioned and their bounds/defaults live only in the raw schema. The one useful hint is that the location scoping is the defining filter, but that does not cover the pagination contract.

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 SOPs') with a scope qualifier ('assigned to a site'), which distinguishes it from the global list_sops. However, it never explicitly names any sibling such as list_location_policies or list_location_documents, so differentiation must be inferred from the scope phrase alone.

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 when-to-use or when-not-to-use guidance; the agent is left to infer that this is the per-site variant versus the global list_sops. No prerequisites, no mention of what a 'site' identifier must be, and no routing to alternatives.

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