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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description contributes real added context by disclosing the owner-gating/auth requirement and the hard scoping guarantee. It says nothing about ordering, pagination behavior, or what a caller gets when no events exist, which are the remaining behaviors an agent would want.

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, correctly front-loaded with the resource and followed by the scoping guarantee. It is close to a restatement of the title, so some content is redundant, but there is no filler or 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?

An output schema exists, so return values need not be explained, and annotations cover safety. But for a list tool with three optional parameters and a non-obvious enum ('all_linked' presupposes a wallet-linking concept the description never introduces), the definition leaves out pagination guidance and the meaning of the link scope, which is too much missing for correct invocation.

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 only 33% – only 'filter' is documented, while 'limit' and 'offset' carry bounds but no meaning. The description adds no parameter guidance whatsoever, so it fails to compensate for the gap: an agent gets no hint about page size defaults, iteration strategy, or what 'all_linked' actually spans.

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 and resource ('read the authenticated agent's own reputation event audit trail') and adds a negative scope guarantee ('never returns another subject's events') that separates it from subject-oriented siblings like problee_get_subject_reputation. It does not name any sibling explicitly, so it falls short of full differentiation, but the purpose is unambiguous.

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 'own events' framing implies usage and the 'never returns another subject's events' clause implicitly excludes the cross-subject case, which is the main routing decision an agent faces here. However, it never says when to prefer this over problee_get_my_reputation, nor when to use it at all (audit/debugging vs. score lookup), leaving the agent to infer the choice.

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