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

Annotations already establish readOnly/idempotent/non-destructive safety, so the bar is lower, and the description clears it by disclosing non-obvious behavior: a 15-minute provenance window valid on any replica, the unverified_model_data fallback when no receipt exists, and a verbatim attribution-footer obligation. It stops short of auth, pagination, or rate-limit behavior, but this is genuinely additive context beyond the structured fields.

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 purpose is front-loaded, but the bulk of the text is reusable orchestration boilerplate, and the data-accuracy contract references 'campaign budgets, frequency, ROAS, CPA' — advertising concepts with no bearing on Calendly scheduling data, which reads as template noise. Multiple sentences do not earn their place in a tool-specific definition.

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 seven-action connector with full schema coverage and no output schema, the description covers the data domain and the downstream chart/provenance contract adequately. It omits authentication requirements, pagination semantics, and per-action scope, leaving the agent to rely entirely on the enum descriptions for action-level detail.

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% — the action enum and params object fully document every accepted argument — so the baseline is 3. The prose adds nothing about parameter syntax or formats, which is acceptable given the schema does the work, but it also fails to compensate for anything, so no credit above baseline.

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 opening sentence names a specific resource and four data categories ('scheduled events, event types, invitee lists, and user availability'), so the agent knows roughly what the connector exposes. However, it never enumerates the seven actions the tool actually performs and never distinguishes itself from the sibling calendar_connector, so the purpose stays at a vague level.

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?

Guidance is entirely about downstream orchestration (call chart_render for visuals, pass provenance_token within 15 minutes) rather than when to choose this connector over calendar_connector or any other sibling. The agent can infer that Calendly questions should route here, but there is no explicit when/when-not statement for the tool itself.

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