select_object

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

Annotations indicate destructiveHint=true, but the description fails to disclose any behavioral traits such as what gets deselected, how the active selection changes, or any side effects. The description adds no value beyond what the annotations already state.

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?

While extremely short, this is under-specification rather than conciseness. The single phrase adds no useful information and would be equally unhelpful if slightly expanded. It lacks the structural detail needed for a tool description.

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 completely inadequate for a tool with a required parameter, sibling differentiation, and destructive annotations. It does not explain the selection behavior, interaction with other objects, or return value. Even with an output schema present, the description remains woefully 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?

With 0% schema description coverage, the description must clarify the 'name' parameter. It does not mention that the parameter likely names the object to select or how it should be formatted. The description provides no semantic meaning beyond the schema's basic string type.

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 'Pilih satu objek' directly translates the tool name, making it a tautology. It states verb+resource but provides no additional context about what selecting means in the scene. It does not distinguish this tool from siblings like select_by_type or select_all.

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 given on when to use this tool versus alternatives. Sibling tools like select_by_type, select_all, and find_objects exist, but the description offers no comparison or context for choosing this one.

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