nbc_generate

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

Annotations provide only a title, not read-only or destructive hints, so the description must carry behavioral disclosure. It does not state whether generating a drawing mutates state, creates persistent entities, requires authentication, or affects the document. The 'generate' wording suggests output production, but side effects are left ambiguous.

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 compact and front-loaded with the core purpose, and the operation/data lines are useful. But the trailing 'etc', duplicated 'building' entry, and loose format make it less precise than it could be.

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 tool has a free-form data object, no parameter enums, no parameter descriptions, and several seemingly related sibling tools, the description does not provide enough context to invoke it reliably. The include_screenshot parameter is missing entirely, and the payload examples are too underspecified to guarantee correct usage.

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 does add meaning by listing operation values and data keys like scale, building, grid_x, grid_y, and walls. However, types are not specified, the data object is essentially free-form, and the include_screenshot parameter is completely undocumented.

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 states a specific action ('Generate any Hama-level drawing') and enumerates drawing types with scales, so an agent understands the general purpose. However, it is vague about what distinguishes this tool from siblings like nbc_drawing and nbc_section, so it does not fully differentiate.

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 when-to-use or when-not-to-use guidance is provided. The phrase 'Generate any Hama-level drawing' implies this tool handles everything, but sibling tools such as nbc_drawing, nbc_section, and nbc_wall suggest overlapping or more specialized workflows. The description never explains which tool to choose for a given task.

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