create_schedule

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

Annotations provide no destructive or idempotent hints, and description fails to disclose side effects, permissions, or what happens if a schedule already exists. Minimal behavioral context beyond the creation action.

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?

Two sentences: first states purpose, second adds key parameter flexibility. No redundancy, front-loaded, and every sentence adds 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?

Given the tool's complexity (9 parameters, nested availability object), the description is brief. It omits overarching context about schedules' purpose (recurring availability slots) but output schema and sibling names provide partial context.

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 (89%), so description adds marginal value. It does clarify that owner accepts multiple formats and calendar can be ID or name, which goes beyond the schema's simple 'string' descriptions.

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?

Description clearly states 'Create a calendar schedule' with a specific verb and resource. It adds detail about owner and calendar targeting, distinguishing it from siblings like create_event.

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?

Provides hints about owner and calendar input formats but lacks explicit guidance on when to use this tool versus alternatives (e.g., create_event, create_recurring_event). No when-not-to-use or exclusionary context.

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