nbc_decor

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

Annotations provide only a title, so the description carries the full burden for behavioral disclosure. It explains what object categories fall under 'decor' but says nothing about side effects, permissions, state changes, or operation semantics.

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 short, front-loaded phrase with no filler or repetition. It is easy to scan, though its brevity is partly the reason it lacks semantic depth.

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?

For a required-string-operation tool with an unconstrained data object and zero parameter descriptions, the one-line scope note is insufficient. Even with an output schema, the agent still lacks critical invocation details such as supported operation names and how data should be structured.

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% and the required operation parameter is a bare string with no enum or explanation. The description does not explain valid operation values, the shape of data, or how include_screenshot behaves, so an agent cannot reliably construct arguments.

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 identifies the tool's domain — hatches, fills, symbols, and furnishing blocks — which helps separate it from wall, opening, or drawing siblings. However, it lacks an explicit verb or action, so it is a category label rather than a statement of what the tool does.

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 listed decor-related item types imply when the tool is relevant, and sibling names provide contrast. Yet no explicit alternatives, exclusions, or selection conditions are stated, leaving the agent to infer usage.

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