map_create_blockout

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

With no annotations, the description carries full burden. It mentions both creation and dry-run modes but does not disclose side effects, permissions, or what 'greybox blockout' entails. The default behavior (dry-run) is implied but not explicitly stated as the primary mode.

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 a single sentence, which is concise and front-loads the main action. However, it omits critical details, making it insufficiently informative. It is not overly verbose but is too sparse.

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 absence of output schema and annotations, and the complexity of creating a blockout from a SceneSpec, the description is inadequate. It fails to explain the return behavior, error conditions, or additional context needed for proper 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%, yet the description provides no explanation of the parameters (dryRun, sceneSpec). The meaning of dryRun and the required structure of sceneSpec are left entirely to the agent's inference from the schema, which lacks descriptions.

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 action (create/dry-run) and the resource (greybox blockout from a SceneSpec). It distinguishes the tool's purpose from siblings like map_apply_scene_spec, but could be more explicit about the difference.

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 like map_apply_scene_spec or map_refine_visuals. The description does not mention prerequisites or context for usage.

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