list_items

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

No annotations provided, so description carries full burden. Discloses read-only nature, which is crucial. Does not mention authentication, rate limits, error behavior, return format, or paging behavior beyond limit default. Adequate but with gaps.

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 sentences succinctly convey purpose and capabilities. No filler or redundant information. Front-loaded with the primary action.

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 listing tool with 7 parameters (1 required) and no output schema, the description covers the main capabilities. Lacks pagination behavior (skip not mentioned) and return structure, but overall sufficient given the tool's simplicity and high schema coverage.

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 high (86%), baseline 3. Description adds modest value by labeling filter as 'Mongo-style', sort as 'JSON', and limit with default, but mostly duplicates schema descriptions. No new parameter semantics beyond what schema provides.

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?

Description clearly states 'List content items for a model' with a specific verb and resource. Distinguishes from sibling tools like describe_model (describe), get_item (single item), list_models (models list), and search (cross-model search).

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?

Implicitly clear when to use (listing items of a model with optional filters). Lacks explicit when-not or alternatives though. The sentence 'Read-only' provides context but no exclusionary guidance.

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