nbc_drawing

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

Annotations only provide a title, so the description must carry the behavioral disclosure burden. It reveals the existence of operations like purge and save, but does not explain side effects, destructive consequences, required permissions, or operation-specific behavior.

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 compact sentence that front-loads the resource and then provides a useful list of operations. It is concise and contains no filler.

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 multi-operation dispatcher tool with no annotations and no parameter enums, this description is too skeletal. It lacks per-operation argument details, expected input formats, and any notes on how the output schema varies by operation.

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 for missing parameter documentation. It usefully hints at possible values for the 'operation' parameter, but does not explain 'data' or 'include_screenshot' or how they relate to each operation.

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 as managing drawings and enumerates the supported operations: create/open/save/info/purge/plot_pdf/get_variables/setup_nbc_standards. This makes the tool's core function understandable, though it does not explicitly differentiate it from sibling NBC tools beyond the 'Drawing' resource.

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 about when to use this tool versus alternatives, or how to choose among the listed operations. The operation list implies usage, but there is no explanation of prerequisites, typical scenarios, or exclusions.

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