List Bundle Entries

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

The annotations already declare the tool to be read-only, idempotent, and non-destructive. The description adds minimal context by specifying the scope 'in one bundle', but it does not disclose behaviors such as default filtering of archived entries or pagination via the limit parameter.

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 precise sentence that immediately states the action and scope. No wasted words, and it is appropriately sized for a simple listing operation.

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 there is no output schema, the description does not clarify what the response format looks like, nor does it explain how limit or include_archived affect the result. The purpose is clear, but behavioral depth is lacking for a tool with 3 parameters.

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 description coverage is 0%, and the description does not mention any of the three parameters (bundle_id, limit, include_archived). The agent must rely on parameter names and defaults in the schema; the description adds no explanatory value.

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 the specific verb 'List' and identifies the resource as 'notes/entries' with the scope 'in one bundle', which clearly distinguishes this from sibling tools like bundled_list_bundles or bundled_search_entries.

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 provides no guidance on when to use this tool versus alternatives such as bundled_search_entries or bundled_get_entry. It only gives a terse statement of the operation, failing to mention exclusions or preferred contexts.

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