Triage Finding

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

The description states that 'dryRun defaults true', which is a behavioral trait beyond the schema. However, with no annotations provided, it fails to disclose whether the tool modifies state, requires permissions, or produces side effects, leaving major gaps.

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?

Though very short, the description sacrifices essential information for brevity. It is under-specified and fails to earn its place by providing meaningful guidance, making it more cryptic than concise.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain the operation, return values, or side effects, leaving the agent without sufficient 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 0%, yet the description only clarifies the default for dryRun. It does not explain the meaning or purpose of notes, reason, or findingId, which are critical for correct invocation.

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 'Triage Finding' essentially restates the tool name without specifying what 'triage' entails. It lacks a clear verb and resource, making it vague and not helpful for understanding the tool's function.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., confirm_finding, accept_risk). The context of 'triage' is left undefined, and no alternatives or exclusions are mentioned.

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