listScheduledCalls

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

With no annotations, the description carries the full behavioral burden, but it only says 'List' without disclosing pagination behavior, auth/owner scoping, rate limits, or response shape. There is no explicit contradiction, but the description adds little beyond the operation name.

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?

A single sentence with no wasted words and a front-loaded verb+resource. It is concise, though the terseness leaves out meaningful operational detail addressed by other dims.

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 3-parameter list endpoint with no output schema and no annotations, this description omits pagination, return contents, auth requirements, and the meaning of owner_email. An agent cannot fully determine how to call it correctly from the description alone.

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 only 33% and the tool description does not describe any paramters. limit and offset have defaults but no semantic explanations, and owner_email's key-dependent behavior appears only in the schema, so the description does not compensate for the coverage 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?

States a specific verb and resource: 'List planned outbound reminder calls.' The noun phrase clearly differentiates this from siblings like makeInstantCall or listCallLogs, and the scope is explicit without needing a title.

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 on when to use this vs. alternatives, no exclusions, no mention of whether this is for retrieving upcoming scheduled reminders versus call logs or other call-related operations. An agent must infer usage from the tool name.

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