reorder_effects

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

No information is given about side effects, permissions required, reversibility, or error behavior. Without annotations or additional description, the agent cannot anticipate the tool's impact or potential risks.

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 concise at just one sentence, conveying the core operation without unnecessary fluff. It is well-structured and easy to parse.

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?

Given the complexity of the schema with multiple optional parameters, the description is severely incomplete. It does not explain how the parameters relate to the reordering operation, what determines the layer, or what the expected outcome is.

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 input schema lists six parameters but the description does not explain the meaning or purpose of any of them (e.g., compId, layerName, effectIndex). The schema itself provides no descriptions, so parameter semantics are entirely undocumented.

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 'Reorder effects on a layer' clearly states the tool's action and target entity. It is concise and unambiguous, though it does not elaborate on the specific context or parameters involved.

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, prerequisites, or alternatives. It entirely lacks usage context, making it difficult for an agent to decide when this tool is appropriate.

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