snb_get_warehouse_data

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that the tool returns 'Timeseries data from the warehouse cube as Markdown + JSON,' which is useful behavioral context beyond annotations. 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?

Description is well-structured: first sentence states purpose, then contextual sentence, then sibling guidance, then Args/Returns sections. No wasted words; every sentence adds value.

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 tool's simplicity (one object param, no output schema), the description covers purpose, usage prerequisites, return format, and domain context (SNB Warehouse cubes, BSTA banking statistics). With rich annotations, it is complete.

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 effectively high (all parameters have descriptions in schema). The description adds minimal extra parameter info beyond restating schema details, so baseline of 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?

Description clearly states 'Retrieve raw data from any SNB Warehouse cube by ID.' It specifies the verb (retrieve), resource (SNB Warehouse cube data), and distinguishes from siblings like snb_get_warehouse_metadata (which gets structure) and snb_list_warehouse_cubes (which discovers cube IDs).

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?

Explicitly instructs to use snb_get_warehouse_metadata first to understand cube structure and snb_list_warehouse_cubes to discover available cube IDs, providing clear when-to-use guidance and alternatives.

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