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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one useful behavioral detail—third-party documents are linked at their source—but does not describe result ordering, pagination, or what the document records contain.

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?

The definition is a single front-loaded sentence that begins with the action and resource, then gives scope and document types. The long type list is somewhat repetitive of the enum but still useful for quick comprehension, and there is no filler.

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 two-parameter list tool with no output schema, the description covers the main scoping modes and notes that third-party docs link out. It is still missing practical details such as what fields each returned document includes and whether results are paginated or ordered.

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 50%: the series parameter is documented as accepting a find_series id or name, while type is an enum. The description reinforces the type values and the 'across the site' behavior, but it omits the 'other' enum value and does not clarify that both parameters are optional or how they combine.

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 and resource ('List the documents Oxbox Energy publishes') and explains the two supported scopes: by series or by document type across the site. It distinguishes the tool's content from generic series lookup, but it does not explicitly name or differentiate it from siblings like search or fetch.

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?

The description implies usage through its two filtering modes ('for a series, or of one type across the site'), which helps an agent understand how to call it. However, it gives no explicit guidance on when to use this instead of search, fetch, or find_series, and it does not state exclusions or prerequisites.

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