get_vertex_list

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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing: not the number of vertices returned, their coordinate system, ordering, or what happens if solid_id is invalid.

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 short sentence with no filler, but it is arguably too terse given the ambiguity of 'bbox corner vertices'. Every word earns its place, yet more structure was needed.

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?

With no annotations, no output schema, and an undocumented parameter, the definition is incomplete for a data-returning tool. The return format is the most important thing an agent needs here and it is entirely absent.

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 there is one required parameter, solid_id. The description implies it identifies a solid but gives no format guidance (name vs. handle vs. UUID), leaving the schema's untyped string ambiguous.

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 verb ('Return') and a resource ('solid bbox corner vertices'), so the basic operation is identifiable. However, the phrasing is compressed jargon and does not distinguish it from siblings like get_edge_list, get_face_list, or measure_bounding_box.

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 indication of when to use this tool versus alternatives such as measure_bounding_box or get_topology, and no prerequisites or exclusions stated. Usage is only weakly implied by the phrase 'solid bbox'.

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