run_verification

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

With no annotations, the description must disclose all behavioral traits. It mentions the allowlist constraint but fails to specify whether the command is read-only or destructive, authentication requirements, or side effects. For a verification tool, safety and permission context are critical but absent.

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?

Two sentences that front-load the action and constraint. Every word adds value, with no repetition or filler. Highly concise and well-structured.

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 tool lacks an output schema, so the description should explain what the tool returns (e.g., exit code, stdout). It also assumes a valid session but does not mention session prerequisites or lifecycle. For a command execution tool, these omissions leave gaps for the agent.

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 coverage is 100%, so the description adds little beyond the schema. It reiterates the command allowlist constraint (already in the enum) but does not explain 'timeout_seconds' or 'session_id' beyond the schema defaults. Baseline 3 is appropriate.

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 specifies the action ('Run'), the resource ('verification command'), and the context ('within a Direct session'). It also states a key constraint ('Command must be in the Direct allowlist'), which helps distinguish this from siblings like 'run_direct_verification_bundle'.

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 context (whitelisted commands in a Direct session) but does not explicitly state when to use this tool versus alternatives (e.g., 'run_direct_verification_bundle' for bundles). No when-not-to-use guidance is provided.

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