get_bundle

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

Beyond the annotations, the description discloses that the call creates/changes/deletes nothing, that auth is injected server-side, that calls are throttled and retried on 429/5xx, and that non-2xx responses surface as tool errors with specific status meanings. This substantially exceeds the annotation hints.

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 well organized with clear Behavior, Returns, and Use when sections, and most sentences add value. Minor redundancy exists: 'Get a bundle' overlaps with the following sentence and the READ-ONLY label, but the overall structure is efficient 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 single-parameter read-only lookup with no output schema, the description is complete: it specifies the endpoint, auth behavior, rate limiting, retry policy, return format, and error semantics. An agent has everything needed to invoke and interpret the result correctly.

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 single parameter id is already fully described in the schema as 'Unique identifier of the bundle,' providing 100% coverage. The description only rephrases this as 'provided bundle id' without adding format, constraints, or examples, so the baseline of 3 applies.

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 verb and resource: 'Get a bundle' and 'Returns the bundle specified by the provided bundle id.' It clearly differentiates this singular lookup tool from the plural sibling get_bundles, and the read-only nature is explicit.

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 'Use when' section explicitly says it is safe to call speculatively for lookups and reporting, and instructs not to use it for changes, directing the agent to the matching write tool. It also points to the related get_bundles tool, giving clear routing context.

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