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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds a genuinely new behavioral fact: synthetic test activity is excluded from results. With no output schema present, naming the returned aggregates (distribution, best streaks, progress) also adds useful disclosure, though no aggregation window or freshness is specified.

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 short sentences, front-loaded with the operation and payload, followed immediately by the one non-obvious caveat. Nothing is padded or repeated from the title.

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 single-parameter read tool with full annotations, the description covers purpose, returned data, and a data-hygiene caveat, which is nearly everything an agent needs to invoke it correctly. The only omission is the time window over which streak statistics are computed, which could affect interpreting results.

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?

There is a single required parameter with 100% schema description coverage, and the schema already tells the agent to obtain campaignId from list_programs. The description contributes nothing further about the parameter, which is acceptable at baseline 3 given the schema does the work.

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 ('Read') plus a clearly bounded resource and enumerates the returned content: streak distribution, best streaks, and progress for a program. That is much more informative than a restatement of the name, though it does not explicitly distinguish itself from nearby siblings like get_streak_badge or get_goal.

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?

There is no explicit statement of when to call this versus alternatives such as get_streak_badge or get_goal; the use case (per-program streak analytics) is only implied by the wording 'for a program'. 'Excludes synthetic test activity' is a data-scope note rather than usage guidance.

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