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

readOnlyHint already declares the safe-read profile, and the description adds value beyond that: the concrete endpoint (GET /api/v0/activities), the supported query features (_page/_limit/_fields/_filters/_search), and the return envelope { meta, response }. It doesn't cover rate limits or auth needs, but discloses return shape and capabilities.

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 dense sentence plus endpoint and return-shape clauses; every phrase carries information and the core purpose is front-loaded. No filler or redundancy.

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 list tool with fully documented parameters and no output schema, the description supplies the endpoint, supported query modes, and the { meta, response } envelope, which compensates for the missing output schema. Auth and filtering edge cases are not addressed but are not essential 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 100%, so each of the 5 parameters is already fully documented with defaults and syntax. The description merely restates which query features exist without adding format or semantic detail beyond the schema, warranting the baseline 3.

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+resource ('List activities') and enumerates what an activity is (notes, emails, calls, meetings) logged against objects, which clarifies the domain. It does not explicitly differentiate itself from siblings like get_activity or create_activity, but the list scope is clear from the name and text.

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 implies usage (listing activities across objects) and mentions the underlying API endpoint, but gives no explicit when-to-use, when-not, or routing to alternatives such as get_activity for a single record or accelo_request for arbitrary calls. Guidance is only implied.

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