The issuer's paperwork

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

With no annotations present, the description carries the full burden and does substantial work: it discloses the returned data (documents, CDN ETag, Last-Modified, token mapping, watched pages, last-change times) and the filtering behavior. It does not explicitly mention pagination, ordering, or read-only semantics, but for a list-style tool this is reasonably transparent.

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 dense sentences convey a large amount of useful detail without filler. The scope, metadata fields, watched pages, and filter values are all presented compactly and front-loaded.

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 tool with one optional enum parameter and no output schema, the description covers the main return contents and filtering options well. It lacks explicit guidance on default behavior without a kind value and does not clarify how the watched-pages portion relates to sibling tools, but overall it provides enough context for correct invocation.

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%, but the description compensates by explaining that 'kind' is a filter and by listing all valid values exactly matching the schema enum. It does not state what happens when kind is omitted, but for a single optional parameter this is adequate.

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 clearly identifies the tool's resource: every document the issuer publishes plus watched pages, with metadata and filtering. It lacks an explicit retrieval verb like 'list' or 'get', and it includes corporate-action content that overlaps with a sibling tool name, but the intent is unmistakable.

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?

No guidance is given for when to use issuer_documents instead of siblings such as corporate_actions, history, or events. The kind filter is explained, but there are no exclusions, prerequisites, or references to alternative tools.

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