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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it lists every table across multiple domains, includes a one-line description, and explicitly notes whether no-key access can read each table. It doesn't mention pagination or response size, but for a zero-parameter listing tool this is a minor gap.

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 a single, information-dense sentence that front-loads the core action and scope, then lists the output fields and the 'call this first' instruction. Every clause earns its place; there is no redundancy or filler.

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 zero-parameter, read-only listing tool with no output schema, the description is nearly complete: it names the warehouse, the domains, the output fields, and the access caveat. The only missing context is the response format (e.g., whether results are paginated or returned as a single list), but the 'call this first' instruction and the sibling set make the tool's role clear.

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 provides no parameter semantics to clarify. The description compensates by explaining what the tool returns and the scope of the listing. A baseline of 4 is appropriate for a no-parameter tool whose description adds meaningful context about the output.

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 states a specific verb ('List') and resource ('every table in the Strasmore US market-data warehouse'), enumerates the domains covered, and specifies the exact output fields (one-line description, history-window column, no-key read access). This clearly distinguishes it from siblings like describe_table and run_sql.

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 says 'Call this first,' which is strong usage guidance for an agent exploring the warehouse. It also implicitly distinguishes this from describe_table (which presumably details a single table) and run_sql (which queries data), and the no-key access mention tells the agent when this tool is relevant.

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