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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Change a calendar's name,' which is a write operation, but doesn't state whether the operation is reversible, requires special permissions, or affects existing events. No mention of side effects or limitations.

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 description is a single sentence, which is concise and front-loaded with the action. However, it is so sparse that it borders on under-specification, but it's not verbose or wasting words.

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 there is no output schema and annotations are absent, the description must provide sufficient context for correct invocation. It lacks information about how to obtain calendarId, whether the name parameter is case-sensitive or length-limited, and any impact on existing events. The sibling list shows many rename tools, so specificity is needed.

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 33%, meaning only the mailbox parameter is described. The description adds no detail about 'name' or 'calendarId' beyond their basic types. Since coverage is low, the description should compensate, but it doesn't explain that 'name' is the new name or that 'calendarId' can be obtained from list_outlook_calendars.

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 states a clear verb and resource ('Change a calendar's name'), so it is not a tautology. But it lacks specificity about what 'calendar' means (e.g., a calendar in Outlook) and does not distinguish it from siblings like rename_google_calendar or rename_outlook_task_list. The name includes 'Outlook', so the resource is clear, but scope could be more explicit.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention similarities to rename_google_calendar or rename_outlook_task_list, nor any prerequisites like needing the calendar ID from list_outlook_calendars. Usage context is entirely implied.

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