list_udfs

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

With no annotations, the description carries the full burden. It discloses the return shape (name, expression, description), which is a behavioral detail, and the verb 'list' implies a read-only operation with no side effects. It does not mention error behavior or permissions, but this is a simple listing tool.

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, front-loaded sentence that contains no redundant words. It efficiently states the purpose and output fields without unnecessary detail.

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?

For a simple listing tool, the description covers the core purpose and output. However, it lacks parameter semantics, usage alternatives, and has no output schema to fall back on, leaving some gaps in the complete picture.

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% and the description provides no information about the 'sessionId' parameter. The description does not compensate for the schema gap, leaving the agent to infer the parameter's purpose and format from the name alone.

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 specifies the action ('List'), the resource ('the model's DAX User-Defined Functions'), and the output fields ('name, expression, description'). This distinguishes it from sibling tools like list_measures or list_roles, which target different object types.

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 implies the use case: call this when you need to inspect DAX user-defined functions. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions or prerequisites beyond the session ID.

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