create_roof_truss

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

No annotations are provided, so the description carries full burden. It mentions 'accurate geometry', 'proper web patterns', 'angled members', and 'realistic connections', but does not disclose whether the tool creates components, groups, or modifies existing geometry. The lack of output schema and side-effect details limits transparency.

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 concise: four sentences covering purpose, types, features, and a resource link. Every sentence adds value with no redundancy. The purpose is front-loaded, and the structure is clear.

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's complexity (9 parameters, no output schema), the description covers purpose, parameter semantics, and provides a resource for detailed guidance. However, it does not explain the output (e.g., grouping, orientation) or how the origin parameter relates to truss placement, leaving some gaps.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by specifying span ranges for each truss type (e.g., king up to 26', fink 20-60'), which is absent from the parameter descriptions. This helps an agent choose type based on span.

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 'Create engineered roof trusses' with specific verb and resource. It distinguishes from generic sibling tools (create_box, create_circle, etc.) by detailing truss types (king post, fink/W-truss) and spans, making it unmistakably for roof trusses.

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 description provides context with span ranges for each truss type (king up to 26', fink 20-60') and recommends a resource for further guidance. While it doesn't explicitly say when not to use, the specificity implies usage for roof truss creation, which is clear given sibling tools are generic shapes.

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