execute_ops

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'validated allowlisted ops request' and 'dry_run' in the parameter note, hinting at safety or validation aspects, but doesn't explain what validation entails, what 'allowlisted' means, potential side effects, error handling, or output behavior. For a tool that executes operations in Blender (likely a mutation), this is a significant gap in transparency.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by a concise parameter note. There's no wasted text, and it's structured for quick understanding. It could be slightly improved by integrating the parameter note more seamlessly, but it's efficient overall.

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 complexity (executing operations in Blender, likely mutations), no annotations, and an output schema exists (which reduces the need to describe return values), the description is minimally adequate. It covers the basic purpose and parameter structure but lacks details on validation, safety, and usage context. With the output schema handling return values, it meets a baseline level of completeness but leaves gaps for effective agent use.

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%, so the description must compensate. It adds a note explaining the 'request' parameter as a 'JSON object with {dsl_version, transaction, dry_run, ops}', which provides some structure beyond the generic schema. However, it doesn't detail what 'ops' contains, the meaning of 'dsl_version' or 'transaction', or provide examples. This partial compensation earns a baseline score, but more detail would be needed for higher marks.

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 purpose: 'Execute a validated allowlisted ops request (DSL v1) in Blender.' It specifies the verb ('Execute'), the resource ('validated allowlisted ops request'), and the context ('in Blender'), making it clear what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'execute_blender_code', which might handle different types of execution.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., what 'validated allowlisted' means), when not to use it, or how it differs from siblings like 'execute_blender_code'. The agent must infer usage from the name and description alone, which is insufficient for optimal tool selection.

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