cad_find_faces

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 says 'Returns deterministic ids', but does not state whether the tool is read-only, requires authorization, or has side effects. For a 'find' operation it is likely safe, but this is not explicitly stated.

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, using a single paragraph with embedded explanations. It front-loads the main purpose and then lists variants. Slight room for improvement by breaking into clearer sentences or bullet points.

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?

The tool is complex with 10 parameters and multiple kind options. The description covers each kind and its relevant parameters reasonably well. However, it lacks explanation of the return format, error handling, and the meaning of 'deterministic ids'. Given no output schema, more detail would be useful.

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?

Since schema description coverage is 0%, the description is crucial. It explains the 'kind' enum and parameters like normal, radius, tolerance, axis, coordinate, max with examples. However, it omits the required parameters documentId, workspaceId, and elementId entirely, leaving their purpose unstated.

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 'Find faces by geometry' which is a specific verb+resource. It lists various kinds (planar_by_normal, cylindrical, etc.) with examples, making the purpose clear. However, it doesn't explicitly differentiate from sibling tools like cad_find_edges, which slightly reduces clarity.

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 on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it. Sibling tools like cad_find_edges or cad_sketch_* are not referenced, leaving the agent without decision support.

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