dba_systemSpace

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

Annotations already declare readOnlyHint and idempotentHint, so the description does not repeat that. It adds useful context: aggregation over all databases and the behavior of the 'persist' parameter (materializes as volatile table). The description is transparent without contradicting annotations.

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 concise (two paragraphs) and front-loaded with the core purpose. The usage guidelines and argument are clearly separated. Minor repetition of 'across the entire Teradata system' and 'over all databases' but overall efficient.

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 tool with one optional parameter and no output schema, the description provides sufficient context: what it shows, when to use it, and the effect of the parameter. It does not describe the return format, but the verb 'Show' implies a display or result, which is acceptable.

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?

There is only one parameter ('persist') and its description in the schema matches exactly the description in the text. Since schema_description_coverage is 100%, the description adds no new meaning beyond the schema, earning a baseline score of 3.

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 verb 'Show' and identifies the resource ('total disk space usage across the entire Teradata system, aggregated over all databases'). It also distinguishes from siblings by naming alternative tools for database-level or table-level queries, making the purpose unambiguous.

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 specifies when to use this tool ('warehouse-wide storage, total system capacity, or overall disk consumption across all databases') and provides clear alternatives ('dba_databaseSpace' for single database, 'dba_tableSpace' for table-level details), offering excellent guidance.

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