Bundle metadata

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

With no annotations, the description carries the full burden. It accurately states the tool returns metadata without event data, but omits important context such as that the bundle must be loaded (implied by 'loaded bundle') and that bundleId is optional if only one bundle is loaded. These are behavioral constraints that should be explicit.

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 sentence that lists many fields, which is efficient but could be more readable with structure (e.g., bullet points). No irrelevant information, earns its place.

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?

Given no output schema, the description provides a solid overview of return fields (schema version, generation time, etc.), covering the main components. It is fairly complete for a metadata tool, though some field details (e.g., what counts include) are implied rather than explicit.

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% (single optional bundleId with description). The tool description adds no extra meaning beyond the schema's own parameter description. Baseline 3 is appropriate.

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 retrieves 'lightweight metadata for a loaded bundle without any event data' and enumerates specific fields, effectively distinguishing it from sibling tools like bundle_overview or those that return events.

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?

No explicit guidance on when to use this tool versus alternatives; the description simply lists what it returns. It does not specify context like 'use for a quick summary before fetching events' or mention that a bundle must be loaded first.

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