snb_get_warehouse_metadata

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by explaining the return value (cube ID, edition date, dimensions) and that it is safe and idempotent. No contradictions.

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 concise (three sentences plus args/returns) and well-structured with clear sections. It could be slightly shorter by omitting the args/returns that mirror the schema, but overall no unnecessary content.

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 presence of an output schema (not shown) and annotations, the description adequately covers the purpose, usage context, and return format. It does not describe pagination or error cases, but for metadata retrieval this is sufficient.

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 input schema already describes cube_id and lang (with enum). The description repeats this information without adding new semantics. With schema description coverage apparently 0% (though schema does have one description), the description provides marginal additional interpretation. Score is baseline 3.

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 metadata and dimension structure for SNB Warehouse cubes, using the verb 'Get' and specifying the resource. It differentiates from sibling tools like snb_get_warehouse_data by explicitly stating it should be used before querying data, and it is distinct from snb_get_cube_metadata since it targets warehouse cubes.

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 explicitly states 'Use this before querying snb_get_warehouse_data,' providing clear guidance on when to use the tool. However, it does not mention when not to use it or differentiate it from snb_get_cube_metadata, which is a similar metadata tool for other cubes.

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