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

No annotations are provided, so the description carries the full behavioral burden. It discloses future-only scope and soonest-first ordering, but omits read-only status, auth requirements, pagination behavior, and return characteristics. A query tool with zero annotations should say more.

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 sentence, front-loaded with the resource and temporal scope, then examples and sort order. Every element earns its place with 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 9-parameter query tool with no output schema and no annotations, the description is thin: it gives purpose and ordering but says nothing about filters, defaults, or how results are formed. The schema descriptions carry most parameter semantics, so it is not wholly inadequate, but important contextual gaps remain.

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 89%, so the parameters are already well documented in the schema. The description adds no new parameter meaning or syntax beyond what the schema provides, which is the baseline when schema coverage is high.

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 the resource ('items') and temporal scope ('dated in the future'), with concrete examples and a sort order. It is clear what the tool returns, although it uses no verb and does not name sibling tools like recent_items or search_items to differentiate explicitly.

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 when-to-use, when-not-to-use, or alternative tools are named. The agent must infer that this is for future-dated items rather than recent items, searches, or feed listings.

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