Set Selection

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

The description adds no behavioral traits beyond the annotations. Annotations mark readOnlyHint as false (modifying) and destructiveHint as false (non-destructive), which the description implicitly matches. However, it doesn't explain the modification behavior (additive vs replacement) that is controlled by parameters.

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 single sentence is concise but under-specified. It omits critical information about the tool's selection modes, making it insufficiently informative for an agent.

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 and high parameter coverage, the description fails to explain the meaning of 'set' in the context of Maya selection (replace, add, deselect). For a simple yet multi-mode tool, this is incomplete.

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?

The input schema has 100% description coverage for all three parameters, so the description adds no additional meaning. Benchmark is 3 when coverage is high.

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 'Set the Maya selection' states a verb and resource but is vague. It doesn't clarify whether it replaces, adds to, or removes from the selection, unlike the sibling 'selection.set_components' which focuses on components. The parameters 'add' and 'deselect' indicate modes, but the description omits them.

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 provided on when to use this tool versus siblings like 'selection.clear', 'selection.get', or 'selection.set_components'. There is no mention of context or prerequisites.

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