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

readOnlyHint=true already declares the safe-read profile, so the description is not obligated to restate it. It adds value by disclosing the supported query modifiers (_page/_limit/_fields/_filters/_search) and the return envelope { meta, response }, but doesn't mention pagination defaults, rate limits, or max result windows.

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?

Three compact sentences: purpose, endpoint, modifiers, return shape. Front-loaded and waste-free, though the endpoint URL and return envelope are somewhat redundant with what the schema and agent context already convey.

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 listing tool with fully documented parameters and no output schema, this covers purpose, endpoint, supported modifiers, and response shape. It stops short of stating pagination semantics or how meta relates to the response array, but the essentials are present.

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%, documenting each of the five parameters with types, defaults, and examples, so the schema does the heavy lifting. The description's shorthand list of the modifiers roughly mirrors the schema without adding syntax or constraints beyond it.

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 (List) and resource (activities), enumerates what an activity is (notes, emails, calls, meetings), and gives the concrete API endpoint. An agent can distinguish this from get_activity and create_activity immediately.

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?

Implies this is the bulk listing tool (and the singular get_activity sibling implies a single-record counterpart), but it never says when to use list_activities vs the generic accelo_request or when not to use it. No exclusions or alternative routing are stated.

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