dba_tableSpace

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

The description mentions the 'persist' parameter which materializes a volatile table, a notable side effect. However, it does not explicitly state that the operation is generally read-only, nor does it mention potential performance costs or permission requirements. With no annotations, this is adequate but not comprehensive.

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 front-loaded with a clear purpose sentence but includes a redundant list of parameter descriptions that repeat the schema. It could be more concise by relying on the schema alone.

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 does not specify the output format (e.g., columns returned for non-persist mode) or the units of space measurement. This omission reduces completeness, especially given the lack of an output schema.

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?

Schema description coverage is 100%, so the baseline is 3. The description's 'Arguments' block largely duplicates the schema's parameter descriptions, adding minimal new meaning beyond the initial purpose statement.

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 'Get' and the resource 'table space used across all tables' with optional filters by database/table name. It distinguishes itself from sibling tools like dba_databaseSpace by focusing on table-level space, though it does not explicitly reference alternatives.

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?

No guidance is provided on when to use this tool versus sibling tools. There is no mention of prerequisites, exclusions, or alternative use cases.

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