list_appointments

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing. 'List' weakly implies a read-only operation, but pagination behavior, the default filter (upcoming), result ordering, and return shape are all unstated.

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 single sentence is front-loaded with no filler, but it is under-specified rather than concise: one line cannot carry a three-parameter tool, and the trailing synonym 'meetings' adds no routing value.

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 list tool there is no output schema, no annotations, and no parameter prose, so an agent gets nothing beyond the bare name and a raw schema. The absence of any statement about default filtering leaves a meaningful behavioral gap.

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?

All three parameters (page, per_page, filter) have 0% schema description coverage, and the description mentions none of them. Critically, the filter enum's default of 'upcoming' is never surfaced in prose, so the description fails to compensate for the schema gap.

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 a specific verb and resource ('List appointments/meetings'), so an agent knows exactly what operation it performs. It does not, however, distinguish it from siblings like list_tasks or list_leads beyond the resource noun, so it stops short of a 5.

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?

There is no when-to-use guidance, no mention of the default 'upcoming' filter scope, and no reference to any alternative tool. The agent must infer everything about applicability from the name alone.

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