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

Annotations only supply destructiveHint=true; the description adds substantive context beyond that, noting it writes billable usage data and targets the Amberflo ingestion host via POST /ingest/. It stops short of disclosing idempotency/retry behavior, auth requirements, or rate limits, so it is good but not exhaustive.

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?

Two front-loaded sentences with zero waste: the operation and write nature come first, then the transport detail. Every clause carries information an agent can act on.

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 6-parameter write tool with no output schema and only a destructiveHint annotation, the description covers what the tool is, that it mutates billable data, and the endpoint. It leaves out operational concerns such as rate limits, duplicate-event handling, and required credentials, keeping it just shy of fully complete.

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 description coverage is 100%, so all six parameters, including the nested dimensions object and optional unique_id, are already documented. The description adds no field-level meaning, so the baseline of 3 applies.

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?

States a specific verb (record/ingest) and resource (a single usage meter event), plus the exact endpoint (POST /ingest/). The 'single' scope and the WRITE label cleanly separate it from the read-oriented siblings like get_usage, get_all_usage, and explain_usage.

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 'WRITE:' prefix and 'record/ingest a single usage meter event' imply when to use it, but the description never names an alternative or states exclusions (e.g., batch vs single, when to prefer explain_usage). Usage is inferable rather than explicit.

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