blender_selection

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

No annotations are provided, so the description must bear the full burden. It discloses the supported operations but does not explain behavioral traits such as how the mode parameter affects selection (REPLACE, ADD, SUBTRACT) or what happens to existing selection. The description adds partial context but lacks crucial details.

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 a single paragraph listing operations in a bullet-like format, which is concise and readable. It front-loads the main purpose. However, it could be slightly more structured (e.g., using a list) for clarity, keeping the score at 4.

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 tool has an output schema, so return values are covered elsewhere. The description enumerates operations and implies corresponding parameters. While it misses some nuance (e.g., how active_object interacts), it is largely complete for a selection tool with well-documented 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 the schema already explains all parameters. The description adds value by mapping operations to parameters (e.g., select_objects uses object_names), but this is only marginal beyond the schema. Baseline score of 3 is appropriate.

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 objects and elements in Blender scenes, and lists several specific operations (select_objects, select_by_type, etc.), making the purpose crystal clear. The tool is distinct from any sibling tool, as no other sibling has 'selection' in its name.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it explain when to prefer one operation over another. The operations are listed, but without context or exclusions, the agent must infer usage from parameter names alone.

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