Get Appointments for Contact

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior; the description adds the concrete OAuth scope 'contacts.readonly' and the HTTP verb, which are useful for invocation. It does not describe pagination or return shape, but the annotation coverage lowers the burden on the description.

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 a single compact line containing the operation, resource path, and required scopes. Every element earns its place, and the core purpose is front-loaded with no filler.

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 simple GET operation with one required parameter and strong annotations, the description plus schema is sufficient to construct a correct call. There is no output schema and no detailed return-value description, but the plural 'Appointments' conveys the general result and the other gaps are minor.

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 100%, so contactId is already documented as 'Contact Id'. The description adds no additional meaning about the parameter's format, source, or constraints, so it does not improve on 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 explicitly states 'Get Appointments for Contact' and gives the exact REST path, making the operation unambiguous. It clearly distinguishes itself from sibling calendar/appointment tools by tying the operation to a contactId resource.

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 path and title imply the tool is for retrieving a contact's appointments, but the description gives no explicit when-to-use guidance or alternatives. With many sibling tools available, an agent must infer selection from the name and endpoint rather than from stated criteria.

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