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

Annotations already declare readOnlyHint=true, and description confirms it's a read operation. It adds context about 'hand-marked' slots and 'within a window', but lacks details on authorization needs, empty results, or rate limits. No contradiction with 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?

Single sentence, no fluff. Perfectly sized for the tool's simplicity (3 parameters, straightforward purpose).

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, so description should hint at return format (e.g., list of time slots). It doesn't. However, tool complexity is low and annotations cover read safety, making it marginally adequate.

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 0%, so description must compensate. It indicates 'email' and a 'window' (from/to), but does not specify that 'from' and 'to' are Unix timestamps or provide format/units. This leaves ambiguity for an AI agent.

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?

Description clearly states it reads hand-marked free slots for an email within a window. Verb 'Read' and resource 'previously hand-marked free slots' are specific, and it distinguishes from siblings like 'set_manual_availability' and 'get_meeting_availability'.

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?

Description implies usage after manual availability has been set, but does not explicitly state when to use this tool vs alternatives like 'get_meeting_availability' or 'find_common_slots'. No exclusion criteria provided.

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