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

Adds the negative behavior 'Does NOT return vector IDs' beyond the annotations, preventing a common mistaken use. Annotations already establish read-only, idempotent, open-world safety profile, so the description only needs to add behavioral specifics.

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?

Three sentences, each with a distinct purpose: what it returns, how to use it, and what it doesn't return with a pointer to the sibling. No filler.

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 single-parameter read-only metadata tool with an output schema present, the description covers purpose, usage, and key exclusions. Nothing an agent needs to select and call it correctly is missing.

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 schema already documents product_id fully with type, description and example (100% coverage). The description adds no additional parameter-level meaning, so the baseline score of 3 applies.

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?

States a specific verb (returns) and resource (StatCan cube metadata) with enumerated contents (dimensions, member trees, frequency, geography, last release). Explicitly distinguishes itself from statcan_cube_vectors by stating what it does not return, making it easy to differentiate.

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?

Gives explicit use case: construct a coordinate string for statcan_cube_data. Names the alternative statcan_cube_vectors for when vector IDs are needed, providing a clear when-to-use/when-not-to-use distinction.

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