schedule_session

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

No annotations provided. Description reveals confirm-gated behavior (important for execution) but omits other behavioral traits like return values, error states, or authorization needs. Minimal but useful disclosure.

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, zero waste. Front-loaded with 'confirm-gated' as key qualifier. 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?

Tool has 7 parameters, no output schema, no annotations. Description covers confirm behavior and subscriptionId but lacks return format, error handling, and parameter details (e.g., meetingLink dependency). Adequate but incomplete.

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 low (14%, only confirm described). Description adds context for subscriptionId (referencing list_subscriptions) and states times are ISO strings. Does not explain clientId, type, meetingLink, or scheduling constraints. Baseline 3 with slight improvement.

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?

Clear verb 'Book' plus resource 'session' with key qualifier 'confirm-gated'. References subscriptionId, distinguishing from list_sessions and other booking tools. Sibling tools include session listing and other actions, making this distinct.

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?

Explicitly states prerequisite (subscriptionId via list_subscriptions) and format (ISO strings). Does not explicitly exclude alternatives or provide when-not-to-use, but context is sufficient for an agent.

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