snb_get_cube_data

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

Annotations declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds that return is raw JSON timeseries data, but does not discuss potential errors or performance. With strong annotations, this is adequate.

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 fairly concise but includes a redundant Args section that mostly restates the schema. It is front-loaded with the main purpose and usage guidance, but the Args section could be trimmed.

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 generic nature, the description covers purpose, prerequisites, parameter source, and return format. With an output schema present, it does not need to detail the response structure, making it complete for the use case.

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 has detailed descriptions for all parameters, so schema coverage is effectively high. The description adds a URL for discovering cube IDs and briefly lists parameter names, adding limited but useful context beyond the schema.

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 raw data from any SNB cube by ID and explicitly differentiates itself as a generic fallback beyond dedicated tools, making its purpose very clear.

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?

It advises using snb_get_cube_metadata first and provides a URL to discover cube IDs, offering clear when-to-use and prerequisite guidance. The mention of 'beyond the dedicated tools' implicitly conveys when to use this generic tool over specialized ones.

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