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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description usefully adds the hard result cap of 100 and the newest-first ordering, which the annotations do not convey. It does not say whether results are paginated or scope-limited, so an agent cannot tell if it is seeing a complete or truncated set beyond the stated cap.

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?

A single eleven-word sentence that front-loads the useful facts: count, resource, ordering. Nothing redundant, nothing padding.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back. It gives count and ordering but says nothing about what fields a conversion record contains or what entity the conversions belong to. For a zero-arg list tool that is close to sufficient, but a single clause on scope would close the gap.

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 takes zero parameters, so there is nothing for the description to compensate for and the baseline is 4. The one implicit parameter-like constraint, the 100-item cap and ordering, is stated in the description.

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 names the resource (conversions) and adds concrete scope: the latest 100, newest first. That is specific enough to distinguish it from record_conversion (a write) and from list_events, though it never explicitly contrasts with any sibling.

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 statement of when to call this versus alternatives, no prerequisite or scope conditions (per-account? per-customer?), and no hint about how it relates to record_conversion or the export tools in the sibling set.

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