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

Discloses traits beyond the annotations: that SSL verification is disabled, that results are paginated with a default of 100, and how to page with offset/limit. readOnlyHint=true is consistent with a read operation. The one gap is that the default-100 result cap's cost implications and what a cube record contains are only partially covered.

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?

Purpose and the sibling alternative are front-loaded, then pagination, then the citation requirement. The mandatory-citation instruction is verbose but operationally necessary, so most sentences earn their place; only minor tightening is possible.

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 two-optional-parameter read listing with no output schema, the description covers scope, pagination, cost (default 100), and required citation of results. The only shortfall is not distinguishing itself from the lite variant, which matters given a 17-tool sibling set.

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 100%, so both limit and offset are already documented in the schema. The description reinforces the pagination model (default 100, use offset/limit) but adds no syntax or semantic detail beyond what the schema provides, so the baseline 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 and resource ('complete inventory of data tables ... including dimension-level details') and even names the underlying endpoint GET /getAllCubesList. Combined with the pointer to search_cubes_by_title, an agent can distinguish this full-listing tool from its siblings without reading either schema.

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 routing guidance ('Prefer search_cubes_by_title if you know what you're looking for') and explains how to page through results. It doesn't clarify when to choose this over get_all_cubes_list_lite, which is the closest sibling, but the core usage condition is stated.

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