tokportal_get_bundle

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it is a safe, non-destructive operation. The description does not add any behavioral context beyond these hints. It does not contradict annotations, so the score is moderate.

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 at four words. While brevity can be good, here it sacrifices clarity. A slightly more informative sentence would not harm conciseness and would better serve the purpose.

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 and the simplicity of a single parameter, the description is still too minimal. It does not explain what the returned bundle contains or how to interpret the response, leaving the agent without essential execution context.

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% for the single parameter 'id' (a UUID). The description 'Bundle ID.' in the schema already explains its meaning. The tool description adds no further context about what identifier formats or bundle types are acceptable, so it does not exceed the baseline.

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 'Get a bundle.' is a minimal tautology of the tool name 'tokportal_get_bundle'. It does not specify what a bundle is, its scope, or how it differs from sibling tools like 'tokportal_get_bundle_video', 'tokportal_get_bundle_account', or 'tokportal_get_bundle_publish_readiness'.

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. With many sibling tools like 'tokportal_list_bundles', 'tokportal_get_bundle_publish_readiness', or 'tokportal_get_bundle_video', there is no context to help an agent choose correctly.

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