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

Goes well beyond the annotations (which only declare read-only=false, openWorld=true, destructive=false) by disclosing the email side effect, the 24-hour guest link validity, the permission roles, the confirm-before-each-call behavior, and the required API key scoping.

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 and most sentences carry real information, though there is mild redundancy ('Add a session... Adds a session at the start and end time you give') and the 'Riverside:' prefix is wasted tokens.

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?

No output schema exists, yet the description covers the key behavioral facts an agent needs (permissions, side effects, link expiry, confirmation). It is nearly complete for this mutation, with only return/response behavior left implicit.

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 100%, so the schema already documents start, end, studio_id, name, and guest_emails. The description reinforces time-zone/start-end and the effect of guest_emails but adds little syntax or format detail beyond the schema, so baseline 3 is appropriate.

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: adding a session to the studio Planner and emailing invitees. The purpose is unambiguous, but it never names the sibling tools (e.g. riverside_update_session, riverside_invite_guest) to route the agent between creating vs updating vs separately inviting.

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?

It gives useful context—who is allowed to schedule (host, owner, admins, directors, editors) and that confirmation is on by default—but provides no explicit when-to-use vs alternatives guidance or exclusions relative to the other riverside_* session tools.

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