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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the description need not restate safety. It adds useful context beyond annotations by emphasizing 'ALL' (no filtering) and specifying the catalog entry fields, including 'the tool name to call' – helpful for an agent deciding what to invoke next.

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?

Two sentences, no filler. The first sentence states the action and output fields; the second gives tactical guidance. Information is front-loaded and every word 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?

For a simple zero-parameter catalog tool, the description explains what will be returned (fields), the scope (ALL), and the intended usage (call first). It lacks only minor details like sort order or pagination, but these are unlikely to be critical for a discovery tool.

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 tool has zero parameters, so the schema fully covers parameter semantics. The description does not discuss parameters, but with no parameters present, there is nothing missing. Baseline 4 is appropriate per the rubric.

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 uses a specific verb ('List') and names the resource ('ALL available AlpineDataWorks intelligence indices'), with the exact fields returned (id, name, domain, grain, tiers, tool name). It clearly distinguishes itself from the many sibling data tools by being the catalog/discovery tool.

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 phrase 'Call this first to discover what you can query' provides clear context on when to use it (before querying any index). It does not explicitly list exclusions or alternatives, but the sibling tools are all individual indices, making this tool's role obvious.

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