save_site

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

The description states the tool saves data (mutation), but the annotation readOnlyHint=true indicates read-only behavior. This is a clear contradiction, scoring 1 as per rules.

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?

Description is concise (3 sentences + example), front-loaded with purpose, and includes a helpful example. Every sentence adds value.

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 7 parameters and no output schema, the description covers the return value, key parameters, and persistence behavior. Minor gaps exist (e.g., error conditions, idempotency), but it is largely complete for a simple save tool.

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 0%, so the description must compensate. It mentions lat, lon, and optional fields, and provides an example. However, it lacks detailed semantics like format constraints or units, making it adequate but not thorough.

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 'Save', the resource 'candidate data-center site', and the context 'to your DC Hub account to track it across sessions'. It also lists key parameters and distinguishes itself from siblings like list_saved_sites which is a listing tool.

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 implies usage for saving sites for later monitoring but does not explicitly state when not to use it or provide alternatives among siblings. The example gives a concrete use case, but no exclusions or comparisons.

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