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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered elsewhere. The description adds only the field list, which duplicates the available output schema, and says nothing about pagination, result limits, or behavior when an agency has no documents.

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?

One well-formed sentence with the scope and the return fields front-loaded; there is no filler or redundancy. 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 one-parameter read tool with a full output schema and complete annotations, the description covers what is needed to call it correctly. The only gap is the unstated relationship to search_guidelines, which would help an agent choose between browsing and searching.

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 100% with a single required parameter, and the description's enumeration of agency names simply restates the schema's own description. It adds no new meaning such as case sensitivity or exact-match expectations, so the 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?

The description states a specific verb ('Lists') and resource ('guideline documents'), scoped to one agency, and enumerates the accepted agency values. It is clear what the tool returns (doc_id, title, version date, source link), but it does not explicitly contrast itself with the sibling search_guidelines, leaving that distinction to inference.

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?

Usage is only implied: an agent can infer this is the browse-by-agency path, while search_guidelines presumably handles keyword lookup, but the description never says so. There are no explicit when-to-use or when-not-to-use statements and no prerequisites mentioned.

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