telivy_list_external_scan_findings

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

No annotations are provided, so the description carries the full behavioral burden. It only states the basic operation and does not disclose response shape, pagination behavior, permissions, or any caveats. 'List' implies read-only behavior, but nothing is made explicit.

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 sentence with no filler. The action and object are front-loaded and efficiently stated.

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 schema covers the parameter, but the definition lacks context about how to obtain the Assessment ID, what the response contains, or how this tool relates to sibling list/get tools. With no output schema and no annotations, the definition is too thin for confident selection and invocation.

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?

The schema provides 100% coverage for the single parameter, describing 'id' as 'Assessment ID.' The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 has a specific verb, 'List,' and a specific resource, 'findings for an external scan.' The plural 'findings' and the word 'List' help distinguish it from telivy_get_external_scan_finding and telivy_get_external_scan. However, it does not explicitly clarify the relationship between an external scan and the required Assessment ID, nor does it contrast itself with sibling tools.

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 guidance on when to use this tool versus alternatives such as telivy_get_external_scan_finding, telivy_get_external_scan, or telivy_get_finding. The intended use is only implied by the tool name and the one-line description.

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