get_udf_list_items

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

The readOnlyHint=true annotation already establishes this is a safe read, so the bar is lower; the description adds the useful note that it wraps NBAPI GetUDFListItems. It does not disclose anything about the returned item structure, pagination, or error behavior for an invalid key.

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?

One compact sentence that leads with the action and resource, with the wrapped-API note as a parenthetical. Nothing is wasted, though the sentence is thin on the information an agent needs.

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 one-parameter read with readOnlyHint and full schema coverage, the description is adequate but not complete: it never clarifies how it relates to get_udf_lists, and with no output schema it says nothing about what an 'item' contains.

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% for the single UDFLISTKEY parameter, so the schema already carries the semantics. The description restates that the key selects a single list but adds no format or syntax detail beyond the schema, which is the expected baseline.

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?

States a specific verb+resource: returning the items of a single UDF list keyed by UDFLISTKEY, and names the upstream API it wraps. However, it never distinguishes itself from the sibling get_udf_lists, which an agent could easily confuse with this one.

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?

There is no explicit when-to-use statement, no mention of when not to use it, and no reference to the sibling get_udf_lists as the alternative for enumerating lists. Only the phrase 'for a given UDFLISTKEY' hints at the required prerequisite.

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