select_all

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the tool is known to modify state and potentially be destructive. The description adds the toggling behavior (select or deselect) but provides no further context about what 'deselect' means, whether it clears the entire selection, or what impact the destructiveHint implies in practice.

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 in Indonesian that immediately conveys the core function. No filler or redundancy; it is optimally concise and front-loaded.

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 is very simple (one optional parameter, no required args), and an output schema exists, so return values are covered. However, the lack of parameter explanation and the vague behavioral disclosure (especially given destructiveHint) leave notable gaps. The description is minimally sufficient but not complete.

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 'action' with a default but no description or enum, and schema description coverage is 0%. The description fails to explain what values 'action' can take, even though the description mentions both selecting and deselecting, which likely maps to action values. This leaves the agent guessing.

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 or deselects all objects ("Pilih atau batalkan semua objek"). This is a specific verb+resource pair that distinguishes it from sibling tools like select_object (single object) and select_by_type (type-based selection).

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 intended use is implied: use this when you want to select or deselect all objects at once. However, there is no explicit guidance on when to prefer this over alternatives like select_by_type or select_object, and no mention of any prerequisites or side effects.

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