tokportal_list_bundles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, clearly framing this as a safe read operation. The description adds no behavioral detail beyond the title, but does not contradict annotations, so a baseline score is appropriate.

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 extremely short (two words), which could be seen as concise, but it under-specifies the tool's purpose. It sacrifices necessary detail for brevity, failing to earn its place by providing minimal value.

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 tool's 7 optional parameters and no output schema, the description should explain the tool's scope (e.g., does it list all bundles for the current user? across all platforms?). The current description leaves significant gaps in understanding what is listed and how filtering works.

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 100%, with seven parameters fully documented in the schema. The description provides no additional context about parameter meanings, acceptable formats, or how they interact (e.g., does platform filter the bundles listed?). Baseline 3 is correct as schema does the work.

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 'List bundles' clearly identifies the verb (list) and resource (bundles), but lacks differentiation from sibling tools like tokportal_list_account_bundles or tokportal_list_bundle_videos. Without context about what 'bundles' are, the agent cannot distinguish this tool from others that also list bundles in different scopes.

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 is provided on when to use this tool versus alternatives such as tokportal_list_account_bundles or tokportal_get_bundle. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision-making information.

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