bridge_create_drawings

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

With no annotations, the description carries full behavioral burden. It discloses content fidelity (actual drawings, no fake dimensions/tags) and optional embedded content, but says nothing about permissions, prerequisites (e.g., project must exist), side effects, reversibility, or failure modes for a creation operation.

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?

A single dense sentence that front-loads the core action ('Create actual drawings') and appends content/constraint details. No filler, though the clause after the semicolon is slightly terse.

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 creation tool with no annotations, no output schema, and 0% schema description coverage, the description leaves critical gaps: parameter semantics, prerequisites, return value, and failure behavior. It provides only content hints, not enough to invoke correctly.

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% for two required parameters, and the description never explains what 'project' expects or what shape/fields 'drawings' array items require. It hints that drawings can contain level views and schedules, but this is not tied to the parameter structure.

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?

States a specific verb+resource ('Create actual drawings') and enumerates what the created drawings contain (embedded level views, optional native schedules/text titles). It implicitly differentiates from preview/inspect siblings via 'actual drawings' and the exclusion of 'fake dimensions or tags', though it doesn't name an alternative tool.

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?

Gives no when-to-use or when-not-to-use guidance relative to siblings like bridge_render_view, bridge_inspect_drawings, or bridge_preview_on_copy. The constraint 'no fake dimensions or tags' is a content rule, not a routing rule.

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