Get XGR MultiBundle reference

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

With no annotations, the description should disclose behavioral traits. It only says 'explains', implying a read-only operation, but does not explicitly state it does not modify state or require authentication. The output format is also not described.

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 concise with two sentences, no redundant text, and front-loads the usage context. Every sentence provides essential information.

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?

Despite being a simple tool, the description fails to specify the return value or output format, which is critical since there is no output schema. The agent cannot fully anticipate what the tool will provide.

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?

The tool has no parameters, so the input schema is trivial. The description adds value by explaining the tool's purpose and usage, exceeding the minimal baseline of 3 for high schema coverage.

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 explains the canonical xgr-multi-bundle@1 format and is to be used before generating a bundle. The verb 'explains' and specific resource 'xgr-multi-bundle@1 format' provide good purpose clarity, though it could be more precise about output.

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 gives a clear usage context ('Use this before generating...'), implying it's a preparatory step. However, it does not explicitly mention when not to use it or compare with alternative tools like get_xgr_multibundle_schema.

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