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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing: no default limit (30), no pagination behavior, no auth needs, and no mention that the tool also supports geographic radius/bbox search despite four geo parameters in the schema. Only the implicit recency ordering is communicated.

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 tight sentence with the filters front-loaded after the core action. Efficient, though it is arguably too terse given the tool's breadth (under-specification is penalized under completeness rather than here).

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 12-parameter tool with zero annotations and no output schema, a one-line description is inadequate. Geo search, pagination defaults, sort semantics, and the before_id/distance incompatibility are all absent from the prose even though an agent needs that framing to invoke it correctly.

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 92%, so the schema already documents params like lat/long/bbox/radius/before_id well. The description adds only the mapping of collection/source/kind filters, which the schema covers anyway; baseline 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?

States a clear resource (items) with an implicit ordering (newest) and optional narrowing filters. An agent can tell it's a recency-ordered listing tool, but it never distinguishes itself from close siblings such as search_items, feed_items, or upcoming.

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 phrase 'optionally narrowed to a collection, source or kind' hints at filter scenarios but gives no when-to-use guidance, no prerequisites, and never names an alternative tool for the non-recency cases (search_items, feed_items). The agent must infer routing.

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