get_finding_by_id

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get detailed information' without specifying what 'detailed' includes, whether the operation is read-only, how errors are handled (e.g., not found), or any other behavioral context. This leaves significant room for ambiguity.

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 is front-loaded with the action and target. Every word is relevant and there is no redundant or filler content.

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 lookup tool with one parameter, the description is adequate but incomplete. It does not describe the return format or the degree of detail, and without an output schema, this information is missing. The differentiation from sibling 'search_findings' is only implicit, so there is room for more contextual guidance.

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 parameter description ('The finding ID or slug to search for') matches the tool description and already exists in the schema. Since schema description coverage is 100%, the description does not add additional meaning or clarify parameter formats beyond what the schema provides.

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 the tool's function with a specific verb ('Get') and resource ('finding by its ID or slug'). It distinguishes this tool from the sibling 'search_findings' by focusing on retrieving a single, specific finding rather than performing a search.

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 gives no explicit guidance about when to use this tool instead of 'search_findings'. It implies usage for looking up a known finding by ID/slug, but does not mention exclusions or alternatives, so the agent is left to infer the appropriate context.

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