list_bundle_ids

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

No annotations are provided, so the description must suffice. It correctly implies a read-only list operation, but does not mention pagination, rate limits, or default behavior for the limit parameter. The limit schema hints at pagination but is not described.

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 a single, efficient sentence that conveys the purpose, return fields, and filtering options without unnecessary words. It is well-structured and front-loaded.

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 simple list tool with optional filters, the description is largely complete. It mentions the return fields. The only missing aspects are default ordering and explicit pagination handling, but the limit parameter covers this implicitly.

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 coverage is 100% and the schema already describes the parameters. The description adds the list of return fields (identifier, name, platform, seed ID) which is not in the schema, providing some extra context, but it repeats the filtering capability already in the schema.

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 'List registered bundle IDs' with specific fields (identifier, name, platform, seed ID) and mentions filtering by identifier or platform, making it distinct from sibling tools that deal with other resources.

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 indicates when to use (when listing bundle IDs) and mentions filtering options, but does not explicitly exclude cases or compare to alternatives. However, the sibling tools are for different resources, so confusion is unlikely.

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