crm_book_meeting

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

Without annotations, the description should disclose side effects, safety, and authentication needs. It only mentions routing under JWT/tenant/company scope but does not state whether the tool is destructive, whether it sends notifications, or what changes occur in the CRM.

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 short (two paragraphs plus an Args list) with no unnecessary repetition. It is reasonably well-structured, though the first paragraph focuses on implementation routing rather than purpose.

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?

Despite having an output schema, the description does not explain the return value or what constitutes a successful booking. The tool's effect on the CRM, the meaning of 'objective', and the expected input format remain unclear, leaving significant gaps.

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 0%, so the description must add meaning. It describes 'message' as a 'free-text objective' and 'inputs' as an 'optional JSON string of structured inputs', but provides no examples, allowed keys, or format details, leaving the agent guessing.

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 states it runs the 'book_meeting' domain agent action, but does not clarify what booking a meeting entails (e.g., create a calendar event, update a CRM record). The name and sibling 'crm_propose_meeting_slots' suggest it is the actual booking step, but this is not made explicit.

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 is provided on when to use this tool versus alternatives like 'crm_propose_meeting_slots'. There is no mention of prerequisites, such as needing a proposed meeting slot, nor any exclusion criteria.

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