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

The annotations already declare readOnlyHint=true and destructiveHint=false, which cover the safety profile. The description's 'Fetch' aligns with this, but it adds no additional behavioral context such as pagination, rate limits, or return format. Since annotations carry the primary burden and description is consistent, a 3 is appropriate.

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?

The description is a single, short sentence that is directly front-loaded with the core action. No wasted words. It is concise and to the point, suitable for a straightforward fetch tool. Slightly more detail on output could be added, but it is appropriately brief.

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 one required parameter, no output schema, and read-only annotations, the description is adequate for a basic call but misses context that would help an agent understand the return shape or any limitations. It does not mention that it returns a list or any filtering options. Given the simplicity, it is minimally complete, but not fully comprehensive.

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% per context signals, so each parameter has a description (e.g., 'Maker address.', 'Activity limit.'). The description adds no extra meaning beyond these minimal definitions. Baseline is 3 when schema covers all params, and the description does not compensate further.

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 states a clear verb ('Fetch') and a specific resource ('maker-level fund activities'). It distinguishes from sibling tools like peer_indexer_deposits_fund_activities by specifying 'maker-level' rather than deposit-level, so an agent can grasp the scope. However, it doesn't elaborate on what 'fund activities' include, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives (e.g., peer_indexer_deposits_fund_activities or peer_market_maker_history). It does not mention prerequisites, context, or any conditions that would select this tool. An agent must infer usage solely from the name and schema.

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