Set Component Selection

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

Annotations do not provide much (all false). The description says 'select' but does not disclose that by default the selection is replaced unless add/deselect are true. No mention of error handling, behavior with multiple objects, or valid notation limitations.

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?

Single sentence, front-loaded with action and notation examples. No unnecessary words.

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?

Despite having an output schema, the description is too brief. It does not explain behavior with add/deselect, return value, or error cases. Incomplete for a tool with multiple boolean parameters.

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 baseline is 3. Description adds examples of valid Maya notation but does not explain semantics of add/deselect beyond what schema provides.

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 tool selects mesh components using Maya notation, with specific examples. It distinguishes from sibling tool selection.set (for objects) but does not explicitly contrast with selection.convert_components, leaving slight ambiguity.

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 on when to use this tool vs alternatives like selection.convert_components or selection.set. No context on prerequisites or typical use cases.

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