List packages

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

It discloses important behavioral traits: packages are not returned with prices by default, enabling include_pricing triggers one Packages.get call per package, and there is a 25-package limit. These details add value beyond the annotations, which already declare read-only, idempotent, and non-destructive behavior.

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 description is concise and well-structured, front-loading the core purpose, then adding essential behavioral notes. Every sentence serves a purpose, and there is no redundancy or fluff.

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?

The description is fairly complete for a listing tool: it covers pricing behavior, full mode, and the underlying API methods. It does not detail every parameter or the exact return format, but those are either in the schema or acceptable for a list operation.

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?

The description adds meaning to include_pricing (how it works, the 25-call limit) and full (raw objects incl. descriptions), which are not fully explained in the schema. However, it does not elaborate on other parameters like include_hidden or package_group_id, and schema coverage is 63%, so it only partially compensates.

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 clearly states the tool lists packages and package groups, specifying it wraps Packages.getAll and Packages.getAllGroups. It also distinguishes from a single-package retrieval tool like get_package by its list nature, making the purpose unambiguous.

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 gives explicit guidance on when to set include_pricing and warns about the 25-package limit, implying filtering before enabling pricing. It does not explicitly contrast with alternatives like get_package, but the context makes the intended use clear.

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