List Bundle

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

Description adds no behavioral info beyond what annotations already provide. Annotations declare readOnlyHint=true and openWorldHint=false, but description does not mention pagination, filtering, or other behaviors.

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?

Very concise but under-specified. The three-word description misses essential details for correct tool selection and usage.

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 the number of sibling tools and the complexity of bundle-related entities, the description is too vague to be complete. Output schema exists but description fails to clarify the scope of 'bundle'.

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% with a detailed description for the 'fields' parameter. Description does not add parameter-specific info, so 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?

Description says 'List Share Links', but tool name is 'List_Bundle'. There are sibling tools like 'List_Bundle_Download', 'List_Bundle_Notification' etc., so it's unclear if this lists all bundles or just share links. The verb 'List' is clear but the resource is ambiguous.

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 guidance on when to use this tool vs alternatives. The description is a single phrase with no context about prerequisites, exclusions, or typical use cases.

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