Location Add

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

Annotations already state that this is a non-readonly, destructive operation. The description complements them by indicating the specific side effect — creating a new location — but it does not disclose additional behavioral context such as duplicate handling, coordinate validation, or whether existing locations can be overwritten.

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, front-loaded sentence with no filler or redundant information. Every word contributes to the tool's purpose.

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 simple creation tool with a fully documented nested payload schema, annotations, and an output schema, the description is mostly sufficient. It could be slightly stronger by explicitly naming the sibling edit tool, but 'new' and the sibling list already provide enough contextual signal.

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 has 100% description coverage and documents the required payload fields, including location, lat, lng, and the optional fixed_coordinates default. The description itself adds no parameter-level detail, so it meets the baseline but does not exceed it.

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 and resource: 'Add a new location to LibreNMS.' The word 'new' clearly signals creation, distinguishing it from sibling tools like location_edit, location_delete, and location_set_maintenance.

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 clearly implies this tool is for creating a new location, which gives basic selection context. However, it does not explicitly mention alternatives, prerequisites, or when not to use the tool, leaving some guidance to inference.

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