dba_sessionInfo

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

No annotations are provided, so the description carries the full burden. It discloses that setting 'persist' materializes a volatile table and returns its name, which is a behavioral trait beyond a simple read. However, it does not mention permissions, side effects on database, or whether the operation is read-only by default.

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: two lines for purpose plus a bulleted list for arguments. Every sentence provides necessary information without redundancy.

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?

Given the complexity of the tool (simple getter with two optional params) and lack of output schema, the description is adequate but could be improved by mentioning what fields are returned (e.g., user, session ID, status). The presence of sibling tools suggests more context would help.

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?

Input schema coverage is 100%, and the description essentially repeats the schema descriptions of 'user_name' and 'persist' without adding new semantic meaning. Baseline 3 is appropriate as the schema already explains the parameters adequately.

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 'Teradata session information for user', making the purpose easily understood. However, it does not differentiate from sibling tools like dba_userDelay or dba_userSqlList.

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 explains how to use parameters (e.g., '*' for all users) but gives no guidance on when to use this tool versus alternatives like dba_userDelay or dba_userSqlList. No exclusions or conditions are provided.

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