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

With no annotations provided, the description carries the behavioral burden. It discloses three key traits: the data is append-only (no updates/deletes), trends are descriptive rather than predictive, and missing coverage is explicitly flagged rather than silently treated as zero. This goes well beyond the name and helps an agent interpret results correctly.

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 dense sentence that front-loads the core fact ('Append-only adoption history') followed by the secondary outputs. It is compact and efficient, though slightly long; it could be split, but it earns its place.

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 no-parameter, no-output-schema tool, the description captures the essential semantics: what is returned, the nature of the data (append-only), and a critical data interpretation rule (missing not as zero). This is sufficient for an agent to invoke the tool and understand the response shape. Minor omissions like explicit output format are not critical here.

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 has zero parameters, so the baseline is 4. There is no parameter information to add, and the description correctly stays silent about parameters, avoiding redundancy.

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 specifies the tool's output: append-only adoption history, descriptive recent-usage trends, and explicit alerts. This distinguishes it from likely siblings like get_adoption_snapshot (a snapshot vs. trends) and get_history (adoption-specific), though it does not name those alternatives explicitly.

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 is given on when to use this tool versus alternatives like get_adoption_snapshot or get_measurement. The description implies it is for trends and alerts, but does not state when a caller should choose this over siblings, nor any exclusions or prerequisites.

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