dba_userDelay

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

The description reveals a behavioral trait: when persist=True, it materializes a volatile table and returns its name. However, it does not discuss safety (e.g., read-only vs. mutation) or authorization needs, especially since no annotations are provided. The description partially compensates but leaves gaps.

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?

Description is extremely concise: 3 sentences front-loading the purpose, followed by a clean argument list. No filler words, every sentence adds value.

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 lacks information about return values (default behavior when persist=False). With no output schema, the agent cannot determine what to expect. Additionally, it does not mention data format or pagination. Given the complexity of a query tool, this is inadequate.

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%, and the description merely repeats the parameter descriptions from the schema. No additional semantics are added (e.g., data types, formats, or constraints beyond what's in the schema). Baseline of 3 is appropriate.

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 uses a clear verb 'Get' and specific resource 'Teradata user delay metrics', with scope 'specified date range'. It is distinct from sibling tools like dba_databaseSpace or dba_sessionInfo, which focus on different metrics.

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 provides no guidance on when to use this tool versus alternatives. It simply states what it does, leaving the agent to infer usage context from the tool name alone.

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