Find edges created by a feature

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

The description adds 'deterministic ids' and 'evaluated by Onshape,' which go beyond the readOnlyHint annotation by implying the output is stable and computed server-side. This is useful context for an agent. No contradictions with annotations are present.

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 one concise sentence that immediately conveys the core purpose. It is front-loaded with the key information 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 simple read-only query with four well-documented parameters and no output schema, the description fully explains what the tool returns (edge ids) and how it operates. An agent has enough information to call it correctly without additional context.

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%, and each parameter has a description. The tool description adds no additional parameter semantics beyond the schema. The 'feature' parameter is already explained in the schema as 'Feature id whose edges you want.' Baseline 3 is appropriate given full schema coverage.

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 states a clear verb and resource: find edges created by a feature. It is specific and distinct from siblings like onshape_get_edges or onshape_find_circular_edges because it explicitly ties edges to the feature that created them. The phrase 'deterministic ids' also adds precision about the output nature.

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 given on when to use this tool versus alternatives such as onshape_get_edges or onshape_find_circular_edges. The description does not mention when this tool is preferred or when to avoid it. The usage context is only implied by the name and description.

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