select_objects

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

With no annotations, the description partially discloses behavior by listing modes (replace/add/remove) and the active parameter, implying selection state changes. However, it does not explicitly state side effects (e.g., whether the selection is replaced by default, or if other objects are deselected).

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 extremely brief and front-loaded with the action, which is appropriate for a simple tool. It avoids verbosity, but the brevity contributes to under-specification, hence not a perfect score.

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 incomplete for practical use: it does not explain what the 'objects' parameter expects (e.g., name strings, paths), whether the tool returns anything, or how to reference objects. Given the simple nature, more context would be needed for reliable invocation.

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 description covers mode and active but completely omits the 'objects' parameter, which is the core of what to select. The schema shows it can be an array, object, or string, but no explanation is given, leaving the agent guessing about accepted formats.

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 action ('select objects') and specifies the resource, distinguishing it from sibling tools like list_objects or get_object_info. It also mentions key parameters (mode, active) that refine the operation.

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 no guidance on when to use this tool versus alternatives (e.g., list_objects for querying, apply_modifier for modifying). It explains the mode values but does not give context about when selection is needed or how it fits into workflows.

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