location_edit

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

Annotations already indicate destructive (modifying) and idempotent behavior. The description adds no further context about side effects or updates beyond lat/lng, but does not contradict annotations. Partial transparency due to payload's 'additionalProperties: true' not being clarified.

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?

Single sentence is highly concise and front-loaded, but could be expanded slightly to include usage context without losing efficiency.

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 and annotations, the description is too minimal. It does not explain prerequisites (e.g., location must exist), the scope of updates (payload allows arbitrary properties beyond lat/lng), or return value structure.

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 100% with descriptions for both parameters (location identifier/name, payload with lat/lng). The description adds no additional meaning beyond the schema, meeting baseline.

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 uses a specific verb ('Edit') and resource ('a location in LibreNMS'), clearly distinguishing it from sibling tools like location_add, location_delete, and location_get.

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 on when to use this tool versus alternatives; lacks explicit when-to-use, when-not-to-use, or comparison with siblings like location_add for creation.

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