update_calendar_subscription

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

With no annotations, the description must disclose behavioral traits. It mentions 'change how a calendar appears' but does not clarify if changes are reversible, require authentication, or affect only subscription display. Missing info on what happens to omitted fields (likely unchanged) or return format.

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?

Single sentence listing properties is concise and free of fluff. Could benefit from structured list or bullet points for clarity, but no unnecessary content.

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 8 parameters, no output schema, and many related sibling tools, the description is insufficient. It omits account/password, does not explain return values, and provides no context on how this tool fits into the calendar subscription workflow.

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 0%. The description maps some parameters (color, selected, hidden, name override, reminders) but omits 'account' and 'password' entirely. It adds partial meaning by grouping properties but does not explain semantics like 'selected' vs 'hidden', or the format of 'default_reminders'.

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 clearly states it changes how a calendar appears in the list, listing specific properties (color, selected, hidden, name override, reminders). The verb 'change' and resource 'appearance in list' are specific. It distinguishes from sibling 'update_calendar' which likely modifies the calendar itself.

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 tool versus alternatives like 'update_calendar', 'subscribe_calendar', or 'unsubscribe_calendar'. The description lacks context on prerequisites or scenarios where this tool is preferred.

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