location-tool

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

No annotations exist, so the description must fully disclose behavior. It mentions actions but fails to explain side effects, error handling, authentication needs, or conditional parameter usage clearly. The required parameters in schema conflict with conditional actual use, creating potential confusion.

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 concise and structured by action with hyphens. The opening sentence is slightly redundant but overall it is well-organized 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?

For a multi-action tool with 5 conditional parameters and no output schema, the description lacks critical details—such as mapping parameters to actions explicitly. It omits information about the locationUpdate parameter and fails to clarify that most parameters are only required for specific actions, leaving the agent underinformed.

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?

Schema coverage is 60%, with three parameters having descriptions. The description adds marginal value by noting name vs UUID preference, but does not clarify the locationUpdate object or action enum beyond what schema provides. It does not significantly enhance schema meaning.

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 it performs operations on locations and lists four specific actions (get, create, update, get-labels). However, it lacks differentiation from sibling tools like camera-tool or door-tool, which might overlap conceptually.

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 some usage hints, such as using location names over UUIDs for reports, and notes requirements for update and create actions. However, it does not explicitly guide when to use this tool versus siblings, or when not to use it.

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