Log an activity on a Rootr CRM timeline

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

Annotations indicate readOnlyHint false and destructiveHint false. Description adds that activities are 'auto-linked into the knowledge graph', which is valuable behavioral context beyond annotations. No contradiction.

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 sentences, front-loading the core action. Every clause serves a purpose: activity types, attachment targets, usage context, and CRM background. No wasted words.

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 creation tool with 8 params (2 required) and no output schema, the description covers purpose, usage, and key attachments. Missing details on return value or error cases, but acceptable given tool type.

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 coverage is 50% (4/8 params described). Description clarifies that activities attach to contact/company/deal and that occurredAt defaults to now if omitted, adding meaning 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?

Definition states 'Log an activity (note|call|email|meeting) on a Rootr CRM's timeline' with explicit attachment to contact/company/deal. Clearly distinguishes from sibling tools like rootr_crm_list_activities (listing) and rootr_crm_upsert_task (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?

Says 'Use this to record outreach/history that shows up on the detail view', providing clear context. However, it does not explicitly state when not to use it or contrast with alternatives like task logging.

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