dba_sessionInfo

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

Reveals that setting persist=True materializes a volatile table and returns the table name, which is beyond the schema. However, it does not disclose permissions required, side effects, or what exactly 'session information' includes.

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?

Concise and front-loaded with the purpose. The argument descriptions are clear, though the asterisk quotes are slightly awkward.

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?

Lacks any description of return values for the default case (persist=False). It only specifies behavior for persist=True. Without output schema, the agent is left guessing the format of session information returned.

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 coverage is 100%, and the description repeats the schema descriptions without adding extra meaning beyond the context of 'session information'. Baseline 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?

Clearly states 'Get the Teradata session information for user', which is a specific verb and resource. However, it does not explicitly differentiate from sibling dba_* tools, though the focus on session info is unique.

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 on when to use this tool versus alternatives (e.g., other dba_* functions). The description only lists arguments without explaining context or prerequisites.

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