List follow-up tasks in a Rootr CRM

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds context about being part of a CRM node and auto-linking, but doesn't disclose additional behaviors like pagination details or performance characteristics.

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 concise with two sentences. The first sentence covers purpose and filters efficiently. The second sentence provides extra CRM context, though it is somewhat verbose with parentheticals. Still, it 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?

No output schema exists, and the description doesn't explain what the response contains (e.g., task fields). It covers input filters well but omits pagination behavior and output structure. Given the tool's complexity (9 params), it is adequate 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?

With schema description coverage at 56%, the description helps by listing filterable dimensions (status, assignee, due, contact, company, deal), which adds context for parameters without descriptions (e.g., assigneeId, companyId). However, it doesn't detail syntax or formats beyond the schema.

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 clearly states the action (list) and resource (follow-up tasks in Rootr CRM), and lists specific filterable fields, distinguishing it from sibling tools like rootr_crm_list_deals or rootr_crm_list_companies.

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 what filters can be applied, giving context on when to use. However, it doesn't explicitly mention when not to use or compare to alternatives like rootr_crm_list_activities, but the purpose is clear enough for a list operation.

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