list_bundle_ids

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

With no annotations, the description carries the disclosure burden. 'List' and the per-bundle 'whether used for an app' clarify that this is a read-only enumeration and indicate the output shape, but it does not mention pagination, limiting, auth requirements, or any edge-case behavior. For a zero-parameter read tool, this is adequate but not rich.

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 sentence that leads with the action and resource, then adds the distinguishing return detail. There is no filler or redundancy.

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 tool with zero parameters and an output schema, the description is complete: it states what is being enumerated and what each entry will tell the caller. The presence of an output schema means the return structure need not be repeated in the description.

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 input schema has no parameters and the description adds no parameter-level mechanics, but none are needed. Per the rubric, zero parameters set a baseline of 4.

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 uses a specific verb ('List'), a precise resource ('registered Bundle IDs'), and a distinguishing output detail ('whether each is used for an app'). This clearly separates it from siblings like list_apps and find_app_by_bundle_id.

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 implies the tool's role by naming the operation, but it does not explicitly state when to choose it over alternatives such as find_app_by_bundle_id or list_apps. There is no 'if you need X use this' guidance or exclusion of sibling tools.

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