select_by_type

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

The description does not disclose whether selection replaces the current selection, whether it operates on visible or all objects, or any side effects. Given that annotations include destructiveHint=true, the description should clarify the impact, but it remains silent. No additional behavioral context beyond the annotations is provided.

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 short sentence, which is concise in length but under-specified. It is not verbose, but it lacks essential details. It is front-loaded with the verb, but the overall structure is too minimal to be fully helpful.

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 (not shown), the description does not address return values, selection behavior, or any prerequisites. With annotations indicating destructive potential and a simple parameter, the description is incomplete for safe and correct tool 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 schema has one parameter, object_type, with a default of MESH and zero description coverage. The description only says 'sesuai tipe' (according to type), which minimally maps to the parameter but does not explain valid values, default behavior, or what happens when omitted. The description fails to compensate for the lack of schema documentation.

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 semua objek sesuai tipe' clearly states the tool selects all objects of a given type. It is a specific verb+resource statement, but it does not explicitly distinguish from sibling tools like select_all or select_object.

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 alternatives such as find_objects or batch_delete_by_type. The description lacks any context about selection behavior, replacing existing selection, or when this tool is preferred.

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