Get a person’s calendar for one day

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description adds that the tool requires 'calendar:read' scope and is 'READ-ONLY', confirming safety and specifying the access level. It also lists the specific returned data (time off, overtime, scheduled minutes), adding value beyond annotations.

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 concise sentences with no redundant words. The first sentence immediately states the purpose and output, and the second adds security context. Efficiently front-loaded.

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, so the description must communicate return values. It mentions three data types but lacks detail on the structure (e.g., whether minutes are totals or per-period). Adequate for a simple single-day query, but incomplete for precise usage.

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% with clear parameter descriptions. The tool description does not elaborate on parameters beyond what the schema provides. Baseline score of 3 is appropriate since the schema carries the semantic load.

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 specifies 'Time off, overtime and scheduled minutes for a single person on a single date.' This clearly states the resource (person's calendar), action (get), and scope (single day), differentiating it from sibling tools like get_month_calendar or get_year_calendar.

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 implies usage for a single day per request, but does not explicitly mention when not to use it or recommend alternatives like get_month_calendar for multi-day views. With many calendar-related siblings, more explicit guidance would be beneficial.

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