request_direct_review

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

The description adds behavioral details beyond the annotations: the review is policy-bound, the returned review_id must be passed unchanged, and it expires. It does not contradict readOnlyHint=true or destructiveHint=false, as requesting a review is read-only. It does not disclose denial/expiry failure behavior, but the added flow context is meaningful.

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, zero filler: the first states the purpose, the second states the critical usage constraint. Front-loaded and every sentence earns its place.

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?

This is a complex tool (12 params, a nested operations array, no output schema, and no parameter descriptions), but the description only covers the request/expiry flow. It does not explain how to construct the request per operation_type, what the response contains beyond review_id, or failure semantics. Incomplete for reliable 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?

With 12 parameters and 0% schema description coverage, the description should compensate by explaining parameter roles, but it mentions none of them. The only hint is 'the exact Direct operation to be performed,' implying the fields mirror the operation, yet operation_type enum semantics, path vs source_path/target_path, commands vs operations, and expected_sha256 fields remain completely unexplained. This is a substantial gap.

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 opens with 'Request a policy-bound review for the exact Direct operation to be performed' — a specific verb (Request) and a specific resource (policy-bound review) scoped to the Direct operation domain. This clearly distinguishes it from siblings like audit_session, run_direct_verification_bundle, and apply_patch, making its purpose unmistakable.

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 second sentence provides clear usage context: 'In enforce mode, pass the returned review_id unchanged to the matching operation before it expires.' This tells the agent when the returned value is needed and the time constraint. However, it never explicitly states when to choose this tool over alternatives or when not to use it (e.g., non-enforce mode), so it lacks explicit exclusions.

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