blender_mesh_select_shortest_path

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

There are no annotations, so the description must disclose behavioral traits on its own. It only says 'Select,' leaving unclear whether the selection replaces or extends the current selection, whether edit mode is required, and what happens with invalid indices. This is a meaningful transparency gap for a selection-mutating tool.

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?

Two concise sentences: the first defines the core action, and the second explains typical use cases. There is no filler, and the most important information is front-loaded.

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 description is acceptable for a simple selection tool and the schema fully documents the parameters. However, it omits guidance on selection behavior, prerequisites, and side effects, and there is no output schema to compensate. An agent may need to infer important operational details.

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 100%, so the baseline is 3. The description adds general context about 'mesh elements' and surface paths, but it does not add parameter-level meaning beyond what the schema already provides for index_a, index_b, and mode.

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 specific verb and resource: 'Select shortest path between two mesh elements.' It clearly conveys what the tool does and adds useful context about edge loops and vertex paths, but it does not explicitly contrast itself with sibling tools like blender_mesh_select_edge_loops.

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 gives concrete use cases: selecting edge loops or vertex paths along the mesh surface. It provides clear context for when this tool is appropriate, though it does not mention alternative tools or exclusion conditions.

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