crm_process

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

No annotations exist, so the description carries full burden. It mentions mutation (create/update/cancel) but offers no details on side effects, idempotency, permissions, or failure behavior. The payload format hint is insufficient.

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 short sentences with no wasted words. The structure is efficient, but the conciseness comes at the cost of missing critical information for a tool with this complexity.

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 tool with 0% schema coverage, no annotations, and multi-operation CRUD via a string payload, the description is far too minimal. It fails to explain how actions map to operations, the role of group_id, or error handling, making it incomplete.

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 0%. The description only notes that payload_json contains 'action, event, ...', adding minimal meaning beyond the raw schema. It doesn't explain group_id's purpose or the expected structure/values of the payload fields.

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 states three actions (create/update/cancel) on a 'Booking CRM event', which is a specific verb-resource combination distinguishing it from most sibling tools. However, 'Booking CRM event' is still somewhat vague, and there's no differentiation from the sibling 'crm_context'.

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 guidance on when to use this tool versus alternatives like crm_context. No prerequisites, exclusions, or context for choosing between the three actions are provided.

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