Record a booked meeting

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

No annotations are provided, so the description must carry the burden. It states the tool 'Marks the meeting booked and its tickets scheduled,' which indicates a state change but does not disclose idempotency, permissions, or effects of re-recording. Adequate but lacks depth.

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 two short sentences, front-loaded with the key instruction, and contains no unnecessary words. Highly efficient.

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?

Given no output schema, no annotations, and 4 required parameters, the description covers the main purpose and timing but lacks details on prerequisites, error handling, or behavior on multiple calls. Adequate but not fully complete.

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 high (75%), so the baseline is 3. The description adds no extra meaning beyond the schema; it does not explain the 'meeting_id' parameter which lacks a schema description. No improvement over structure.

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 tool is for recording a meeting after creating the calendar event, using specific verb 'record' and resource 'meeting'. It distinguishes from sibling tools like 'request_meeting' and 'cancel_request' by specifying it as a post-creation step.

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 explicitly states 'After you create the calendar event, record it here.', which provides clear timing for use. However, it does not specify when not to use it or mention alternatives, so it gets a 4.

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