dba_systemSpace

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe reads. The description adds further context by detailing the optional 'persist' parameter and its effect (materializes as a volatile table and returns table name), which goes beyond the annotations. No contradictions.

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 extremely concise with two clear sentences: one for the tool's purpose and one for the argument. Every sentence adds value, and there is no redundant or unnecessary information.

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 tool is simple with one optional parameter and no output schema. The description covers the behavior for both cases (default and persist=True). However, it does not specify the return format for the base case (e.g., a scalar value or table), which is a minor gap. Overall, sufficient for a straightforward 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?

With 100% schema description coverage, the schema already documents the 'persist' parameter. The description repeats the same information ('If True, materializes result as a volatile table and returns table name') without adding new meaning, thus meeting the baseline but not exceeding it.

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 'Get the Teradata total system database space usage', which specifies the verb ('Get') and the resource ('Teradata total system database space usage'). Among sibling tools like dba_databaseSpace and dba_tableSpace, this tool is distinct in focusing on system-level space, making it easy for an agent to select correctly.

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 lacks explicit guidance on when to use this tool versus alternatives (e.g., dba_databaseSpace for database-level space or dba_tableSpace for table-level space). While the purpose distinguishes it, no contextual advice is provided, making it adequate but not helpful for an agent deciding between similar tools.

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