dba_sessionInfo

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds that setting persist=True materializes the result as a volatile table and returns the table name, which is a key behavioral trait beyond annotations. It does not mention any other side effects or limitations.

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 concise with two sentences plus argument list. It front-loads the purpose and efficiently describes parameters. No extraneous information.

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 explains the return value for persist=True but does not describe the default output when persist=False (presumably the session info data). Given no output schema, this is a gap. Annotations cover safety, but return format is incomplete.

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%, with each parameter already well-documented in the input schema. The description repeats these descriptions nearly verbatim, adding no new semantic meaning. Baseline for high coverage is 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?

The description clearly states it retrieves Teradata session information for a user, with the option to get all users via '*'. The verb 'Get' and resource 'session information' are specific. However, it does not explicitly distinguish from sibling tools like dba_userSqlList or base_readQuery, though the name implies session focus.

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. For example, when to use dba_sessionInfo vs dba_userDelay or base_readQuery. No conditions or prerequisites are mentioned.

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