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

readOnlyHint=true already declares this a safe read, so the safety profile is covered. The description adds the activity-type taxonomy and the underlying POST /activities/search behavior, but says nothing about pagination defaults, result ordering, or rate limits beyond what the schema states.

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 tightly written sentences: purpose and subtypes come first, the endpoint detail second. No filler and nothing redundant, so every sentence earns its place.

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 full schema coverage and no output schema, the description supplies enough to call it correctly: what it returns conceptually and the record-scoping model. It stops short of explaining pagination/return shape, but with no output schema that is a minor gap.

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 six parameters (including the parent_id/parent_type pairing and the timestamp bounds) are fully documented in the schema. The description's phrase 'attached to a record' loosely gestures at parent_id/parent_type but adds no syntax or semantics beyond the schema, making the baseline 3 appropriate.

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 the subtypes covered (notes, calls, meetings, system events), and constrains scope to activities 'attached to a record'. Combined with the REST endpoint reference, an agent can distinguish this from copper_log_activity and copper_list_activity_types without opening the schema.

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 gives no when-to-use, when-not-to-use, or alternative tool guidance. It does not say, for example, to use copper_log_activity to create an activity or when parent_id/parent_type filtering is required versus leaving them unset, so the agent must infer usage entirely.

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