Get recent activity

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers little. 'Fetch' implies a read, but there is no disclosure of ordering, time window, pagination, rate limits, or what an 'event' contains beyond the endpoint path.

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 with a parenthetical endpoint and no filler. It is efficient, though the extreme terseness leaves useful context unstated rather than trimming waste.

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 data-fetch tool with no output schema and no annotations, the description should say what constitutes an event, what window 'recent' covers, and the return shape. None of that is present, leaving the agent with an under-specified contract.

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?

With 0% schema description coverage, the description must compensate, and it partially does: 'trimmed to `limit` events' explains that limit caps the number of returned events. However, it adds no boundary info (the schema's max 1000, exclusiveMinimum 0) or default behavior, so the compensation is only partial.

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 ('Fetch recent on-chain events') and even names the backing endpoint (/api/recent), so the agent knows exactly what data comes back. It is distinguishable from siblings like get_collection_stats or get_leaderboard, though it never explicitly contrasts itself with them.

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 use this tool, when not to, or which sibling to prefer for adjacent data (e.g. get_collection_stats vs recent activity). Usage must be inferred entirely from the word 'recent'.

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