Set Mesh Selection

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

The description discloses that the tool replaces the selection and clears existing selection of the specified kind first. Without annotations, this covers the core mutation behavior. However, it does not mention error handling, validation of indices, or other side effects (e.g., destructive nature beyond clearing).

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 two sentences, each earning its place: the first states the primary action and clearing behavior, the second provides a usage guideline. No waste, front-loaded with key action.

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 no output schema and no annotations, the description covers the essential behavior, parameters, and complementary usage. It lacks error or validation details but is sufficient for a simple set tool. The sibling context suggests many related tools, but the pairing note helps.

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% with parameter descriptions, but the description adds value by clarifying that the tool clears existing selection before setting new indices, which is not in the schema. The pairing note also adds context for the 'indices' parameter's purpose.

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 the verb 'Replace' and the resource 'BaseSelect on an editable mesh', specifying the selection kinds (point/polygon/edge) and that existing selection is cleared first. This distinguishes it from sibling tools like 'set_selection' and 'get_mesh', which are mentioned.

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 provides explicit pairing advice: use with 'get_mesh' using 'include:["selections"]' to read channels back. This guides the agent on complementary usage. However, it does not explicitly contrast with alternatives like 'set_selection' or state when not to use this tool.

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