locate_fixtures

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

There are no annotations, so the description must fully disclose behavior. It only states the basic action without specifying whether other fixture attributes are affected, if the operation is reversible, or if it requires specific permissions. For a potentially destructive move, more detail is needed.

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 concise sentence that gets straight to the point. However, it could be more efficient by also including a hint about context (e.g., 'Use to reset positions').

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 zero parameters and existence of an output schema, the description adequately covers the basic operation. However, it lacks behavioral context (e.g., effect on other attributes, whether it's a destructive reset), which is needed for completeness.

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 tool has zero parameters, so the baseline is 4. The description adds meaning by clarifying that the tool acts on 'selected fixtures' and sends them to 'home/default position', which aligns with the parameterless operation.

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 ('Send') and the resource ('selected fixtures') with a specific outcome ('to home/default position'). However, it does not differentiate from sibling tools like 'park_fixture' or 'set_fixture_value' that might also move fixtures.

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 'park_fixture' or 'set_fixture_value'. The term 'Locate' is mentioned in parentheses but without explanation of context or prerequisites.

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