create_dovetail

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

With no annotations, the description must fully disclose behavioral traits. It only states 'Create', which implies mutation but does not explain whether components are modified in place, what happens on failure, or any side effects. There is no mention of expected outputs beyond what may be in the output schema, and no safety or error context.

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 short sentence, which is concise in length but severely under-specified for a tool with 10 parameters. Conciseness should not come at the expense of necessary detail; this is under-description.

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 (10 parameters, no annotations, output schema present but not described), the description is grossly incomplete. It fails to explain parameter semantics, usage context, or behavioral implications, leaving the agent with almost no actionable guidance.

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 description does not explain any of the 10 parameters. The schema provides names, types, and defaults, but no semantic meaning (e.g., how angle affects the joint, what offset components). The description fails to bridge this gap.

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 'Create a dovetail joint between two components' clearly states the verb (create) and the resource (dovetail joint), and specifies the two required inputs (components). However, it does not differentiate from sibling tools like create_mortise_tenon or create_finger_joint beyond the joint type in the name.

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 for when to use this tool versus alternatives. While sibling tool names imply alternative joint types, the description does not explicitly state when create_dovetail is preferred, nor does it mention prerequisites or constraints.

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