boolean_operation

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

Discloses non-destructive nature and that auto tools handle cleanup, but does not detail modifier stack behavior or selection implications. No annotations, so description carries burden; still informative.

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 well-structured paragraphs: purpose and usage note first, then parameter list. No redundant sentences, front-loaded with key info.

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?

Covers purpose, when to use, parameters, and return type. Output schema exists, so return details are sufficient. Complete for a tool with 3 params and no annotations.

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 has no descriptions (0% coverage). Description adds full semantics for all 3 parameters: object_name, target_name, operation with valid values. Adds significant meaning beyond schema.

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?

Clearly states it performs a boolean operation using a modifier, specifying verb and resource. Differentiates from sibling booltool_auto_* tools by noting they handle destructive booleans.

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?

Explicitly says when to use this tool (non-destructive modifier workflow) and when to use alternatives (destructive booleans: use booltool_auto_* tools). Provides clear guidance.

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