location_add

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

The description 'Add' implies a write operation, consistent with annotations (readOnlyHint=false, destructiveHint=true). However, it does not add behavioral details beyond the annotations and name, such as whether duplicate names cause errors or what permissions are required.

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 sentence that is concise and front-loaded with the action. No unnecessary information is included.

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 add tool with good annotations and an output schema, the description is mostly complete. However, it could mention behavior on duplicate location names to improve 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 description itself does not explain parameters; the input schema description covers 100% of parameter semantics. Since the schema provides adequate descriptions, the tool description adds no extra value, meeting the baseline for high coverage.

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 verb 'add' and the resource 'location' to the system 'LibreNMS'. It distinguishes this tool from siblings like location_delete, location_edit, location_get, and locations_list.

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 versus alternatives, such as when to add a new location versus editing an existing one. There are no context or exclusion statements.

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