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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds real value: 'append-only' tells the agent the record is immutable history, and 'returned verbatim' signals no summarization or rewriting of event reasons. It stops short of explaining ordering or pagination behavior.

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 front-loaded sentence that identifies the resource and its scope before the aside. The trailing parenthetical ('NG3 — returned verbatim') is partly cryptic but does carry the verbatim guarantee. No wasted framing.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover safety. However, with two undocumented parameters and a misleading 'every' against a default limit of 100, the definition leaves real gaps for an agent trying to call it correctly.

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 0%, so neither agent_id nor limit is documented anywhere. The phrase 'every ... event' actively misleads about the limit parameter's default of 100, which caps the result set. The description needs to carry parameter meaning here and does not.

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 precisely: an append-only developmental ledger containing growth, pruning, and evaluation events with their reasons. The verb is only implied by the tool name, and no sibling tool is named for contrast, but an agent can tell what it retrieves. The 'NG3' token is opaque jargon that adds no clarity.

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 reach for this tool versus alternatives such as describe_agent or compute_efficiency_report, which likely surface overlapping state. No prerequisites, no scoping conditions, and no exclusions are given. Usage must be inferred entirely from the one-line purpose.

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