apply_drawing_ops

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

With no annotations, the description carries the full burden. It valuably discloses atomicity (all-or-nothing) and a batch cap of 50, but says nothing about failure/rollback behavior, permission requirements, or the destructive nature of ops like delete and revert_to_snapshot. Solid but incomplete behavioral coverage for a write tool.

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?

Three compact sentences, front-loaded with the core purpose and constraint. Nothing is wasteful, though 'the summary' is slightly ambiguous about which tool/artifact it points to.

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 high-complexity tool (nine op types, batches up to 50, atomic mutation) with no annotations and no output schema. The description does not describe the operation categories, return behavior, or failure semantics, leaving the agent under-informed for such a rich schema.

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 0%, so the description must compensate. It meaningfully explains drawingId (with fallback to the selected drawing) and the 50-op cap on ops, but clientBatchId is never mentioned and the nine op types are left entirely to the schema. Partially compensating, not fully.

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?

States a specific verb and resource ('apply ... semantic operations') and a key scope constraint ('Atomically apply up to 50'). The batch-mutation role is clear, and the reference to reading 'the summary first' implies the sibling get_drawing_summary, though no alternative is named explicitly.

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?

'Read the summary first' gives an explicit prerequisite/ordering hint, and 'Uses drawingId when provided, otherwise the selected drawing' tells the agent how the target is resolved. It stops short of naming when-not-to-use cases or explicit alternatives, but the context is clear.

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