List Tables

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

The description mentions it returns tables and context but does not explicitly state it is read-only. Since no annotations are provided, the description carries the burden; however, the nondestructive nature is strongly implied by the purpose of listing.

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?

Extremely concise with no wasted words, well-structured with headings, and front-loaded with purpose. Every sentence serves a clear function.

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?

The description covers purpose, return content, and usage scenarios. It does not mention pagination or limits, but for a list tool with simple output, it is fairly 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?

No parameters exist (schema coverage 100%), so baseline is 4. The description adds value by specifying return fields (row and byte counts, project, organization context) beyond the empty 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 lists all tables in the RawTree project with row and byte counts, using specific verbs and resource. It distinguishes itself from siblings by excluding reading rows (run-query) and describing columns (describe-table).

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 provides when-to-use scenarios (ask what data exists, need table name, verify insert) and when-not-to-use (reading rows, describing columns) with alternative tool names.

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