List activities on a Rootr CRM timeline

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that it lists activities but does not disclose additional behavioral traits such as pagination behavior, response format, or any limitations. With annotations covering safety, the description provides minimal extra value.

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?

Description is two sentences: first states core purpose, second provides CRM context. No redundant information, front-loaded with key action.

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 7 parameters, no output schema, and annotations present, the description leaves gaps: no return value explanation, no pagination details, no behavior when combining filters. The second sentence is promotional rather than informative about tool specifics. Adequate but not 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 57%. Description explains that filtering is possible by contact, company, deal, or activity type, which maps to parameters type, contactId, companyId, dealId. However, it does not explain required parameter crmId or pagination parameters limit and offset. Partial compensation for missing schema details.

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?

Description clearly states verb 'list', resource 'activities', and mentions filtering by contact, company, deal, or activity type. This distinguishes it from sibling CRM list tools like rootr_crm_list_companies, rootr_crm_list_contacts, rootr_crm_list_deals, and rootr_crm_list_tasks.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., rootr_crm_list_tasks). The description only mentions it is part of a CRM node but does not provide context for choosing this tool over siblings for activity-related queries.

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