list_documents

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

There are no annotations, so the description carries the entire behavioral burden. It implies a read operation and lists return fields, but says nothing about the 'refresh' flag (presumably a cache bypass), result ordering, pagination, or whether file URLs are always present; for a two-parameter tool with zero annotation coverage this leaves meaningful gaps.

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 sentences with no filler; the returned-field inventory is front-loaded and the use-case sentence follows naturally. The stray line break is cosmetic, and nothing could be cut 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?

Because there is no output schema, the description's field listing does real work and is the right call. Still, with no annotations and an undocumented refresh parameter, an agent cannot fully predict caching behavior or the shape/ordering of the returned document list.

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 must explain both parameters and does not. docket_id is only obliquely implied by 'in a docket', and 'refresh' — the parameter with the most non-obvious behavior — is never mentioned at all.

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 names the resource ('documents in a docket') and enumerates the document categories and returned fields (documentType, subtype, postedDate, file URLs), so the agent knows what it gets back. It is distinguishable from list_comments and search_dockets, though it opens with a noun fragment rather than an explicit verb.

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?

'Use it to locate the draft guidance, the final guidance, and the notices of availability' gives a concrete use case, which is more than most list tools offer. However, it never states when to prefer a sibling such as get_guidance_text or diff_guidance, nor any exclusion or prerequisite beyond requiring a docket.

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