telivy_get_external_scan_finding

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation is a read ('Get details') but doesn't disclose any potential side effects, authentication requirements, rate limits, or what happens if the slug is invalid. For a read operation, this is a moderate gap but not severe.

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, concise sentence that front-loads the action and resource. Every word earns its place, with no wasted text or 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?

For a simple read operation with two fully documented parameters, the description is mostly complete. However, without annotations or an output schema, it doesn't clarify what the response contains or whether any special conditions apply. The sibling tools suggest a broader security assessment context, but the description doesn't leverage that to add context.

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%, so the schema already documents both parameters ('Assessment ID' and 'Finding slug'). The description adds minimal meaning beyond the schema, only clarifying that the slug identifies the finding. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('Get') and resource ('details for a single external scan finding by slug'), which clearly distinguishes it from sibling tools like telivy_list_external_scan_findings. However, it doesn't explicitly differentiate from telivy_get_finding, which could be ambiguous without further context.

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 usage for retrieving a single finding by slug, but provides no explicit guidance on when to use this tool versus alternatives like telivy_get_finding or telivy_list_external_scan_findings. The context is clear enough for basic use, but lacks explicit exclusions or alternative routing.

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