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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and side-effect behavior are covered. The description adds useful scope (event types covered, property vs wallet) but omits pagination/ordering behavior and the default result cap, which matter for a feed tool.

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 sentences, front-loaded with the core purpose, no filler. The 'and more' and duplicate mention of 'transaction history and event timelines' add slight redundancy but do not bloat it.

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 read-only feed tool with full schema coverage and rich annotations, the description is adequate but thin on behavior an agent often needs: default limit, pagination, ordering, and whether type filtering is server-side. No output schema exists, so return-shape expectations go unaddressed.

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 100%, so all five parameters are already documented in the schema. The description only restates that activity can be scoped to a property or wallet, adding no syntax, format, or filtering nuance beyond the schema. Baseline 3 applies.

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 (Get) and resource (activity feed) with enumerated event types and scope. It is reasonably distinguishable from siblings like get_portfolio or get_property, though it doesn't explicitly call out how it differs from those overlap-prone tools.

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 description indicates the tool covers property or wallet activity, which implies when to use it, but gives no explicit when-to-use vs alternatives guidance, no exclusions, and no mention of sibling tools. An agent must infer the use case.

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