dba_tableSpace

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves table space based on parameters, implying a read operation, but does not mention permissions, performance impact, or side effects. The description is accurate but minimal.

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 sentence that conveys the entire functionality without any extraneous words. It is efficient and front-loaded, making it easy for the agent to parse.

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 includes a return type line ('formatted response with query results + metadata'), providing basic context on output. Given the tool's simplicity and the absence of an output schema, this is adequate. However, for a database tool, additional context on what 'table space' means could be beneficial.

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 0%, so the description must compensate. It provides context for when each parameter is used ('if table name is provided' and 'if a database name is provided'), but does not specify format, constraints, or expected values. This partial compensation warrants a 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?

Description clearly states the verb 'Get' and the resource 'table space'. It distinguishes between two modes: retrieving space for a specific table when table name is provided, or for all tables in a database when database name is provided. This differentiates it from sibling tools like base_tablePreview or dba_tableUsageImpact.

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 when to provide table name versus database name, guiding the agent on parameter usage. However, it does not mention when not to use this tool, alternatives, or prerequisites, so it falls short of a 5.

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