tokportal_get_bundle_video

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety and idempotency profile is clear. The description adds no behavioral detail beyond 'get configuration', but the annotations are sufficient. No contradiction found.

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 of four words, which is extremely concise. It is front-loaded with the action 'Get'. It could be slightly more descriptive without losing conciseness, but it's efficient.

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?

For a simple retrieval tool with complete schema coverage and robust annotations, the description is minimally adequate. It does not explain the return value (no output schema), but for a 'get' operation the concept is straightforward. However, it lacks context about what 'video slot configuration' entails or how to interpret the result.

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%, so the schema already explains both parameters (id as Bundle ID, position as 1-based video slot position). The description adds no further parameter context, 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?

The description clearly states the tool retrieves video slot configuration. The verb 'Get' and resource 'video slot configuration' are specific. However, it does not differentiate from sibling tools like tokportal_configure_bundle_video or tokportal_patch_bundle_video, which also deal with bundle videos. A clear distinction would improve the score.

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 versus alternatives. Among many bundle-video-related siblings (e.g., tokportal_configure_bundle_video, tokportal_patch_bundle_video, tokportal_get_bundle_video? – not a sibling), the description offers no context for selection. It does not mention prerequisites, such as needing to obtain a bundle ID or video slot position first.

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