workflow

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

Annotations are all false (readOnlyHint: false, idempotentHint: false, destructiveHint: false), so the description carries the burden of disclosing side effects. It does not mention that dev_loop executes arbitrary GDScript (potentially destructive), that scene_snapshot may be read-only, or that batch_validate might modify files. No behavioral traits beyond the annotation values are disclosed.

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 concise, using two sentences with no fluff. However, it achieves brevity by omitting three of the six actions, making it incomplete. Every sentence earns its place, but the structure is not fully informative for the tool's actual breadth.

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 is complex: 13 parameters, 6 action types, nested objects, and no output schema. The description covers only three actions and lacks high-level guidance or return-value explanations. It is insufficient for an agent to correctly invoke the full range of functionality.

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 all 13 parameters have descriptions in the input schema. The description adds some meaning for dev_loop by mentioning optional validation, bridge queries, and state saving, but it does not compensate for the actions it omits (create_files, run_verify, diff_scenes). The schema does the heavy lifting, and the description adds marginal value.

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 names three specific actions (dev_loop, scene_snapshot, batch_validate) with clear verbs and resources, giving a sense of the tool's scope. However, it omits three other actions present in the schema (create_files, run_verify, diff_scenes), and the generic phrase 'Development workflow tools' does not fully distinguish it from siblings like script or validation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or when a sibling tool like script or scene would be more appropriate. The description simply lists actions without contextual direction.

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