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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds no behavioral context beyond that — nothing about default ordering, pagination behavior, or the fact that the tool also supports proximity search. The trailing docs URL is a pointer, not disclosure.

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 purpose is front-loaded in a single tight sentence with no filler. The second sentence is attribution boilerplate that earns little place but is short and does not obscure the core statement.

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?

This is a 12-parameter tool with latitude/longitude, bbox, radius, distance sorting, and keyset pagination, and no output schema. The description never signals that location-based querying exists, which is a substantial capability an agent could easily miss when deciding whether to call it.

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 100% across all 12 parameters, so the schema carries the semantics. The description echoes the collection/source/kind filters, which is consistent but redundant, and says nothing about the geo, sort, or keyset-cursor parameters. Baseline 3 applies when the schema does the heavy lifting.

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 resource and scope: 'Newest items, optionally narrowed to a collection, source or kind.' An agent can tell this is a recency-ordered listing tool. It stops short of naming how it differs from siblings like nichedb_search_items or nichedb_feed_items, so sibling differentiation is left implicit.

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' implies the filtering use case, but there is no explicit statement of when to pick this over search_items, feed_items, or upcoming. Usage has to be inferred from the name and the filter list.

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