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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the distinction between the saved cadence and the effective schedule (default when nothing is saved), and the team-workspace rule that the queue belongs to the owner, so members read the owner's schedule. It does not mention rate limits or freshness, hence not a 5.

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?

Front-loaded with the read purpose, then the operational guidance and the team-workspace caveat. Every sentence carries information, though the long parenthetical enumeration of return fields makes the first sentence dense. No filler or repetition.

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?

With an output schema present, the description need not explain return values, yet it does so usefully; the two parameters are fully documented in the schema and the 'days' window is echoed as 'next few days'. The cross-tool handoff instruction and the team-ownership rule close the remaining gaps an agent would face.

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 100%, so a 3 is the baseline. The description goes beyond it by explaining the purpose of the returned slot values and warning that scheduledFor must be passed 'unchanged' to schedule_note, which is a semantic constraint the schema cannot express. It adds modest but genuine meaning over the schema.

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 specific verb (read) and resource (the writer's Note posting schedule), then enumerates exactly what is returned: saved cadence, effective schedule, timezone, next open queue slot, and open slots. This clearly distinguishes it from update_posting_schedule and list_scheduled_items, which an agent can rule out without opening any schema.

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 explicit downstream guidance: to add a Note to the queue, pass nextOpenSlot.scheduledFor or an openSlots entry's scheduledFor unchanged to schedule_note's scheduledFor. That is a concrete use case plus the alternative tool to hand off to. It stops short of stating when not to call it (e.g., versus list_scheduled_items for already-queued items), so it is not a full 5.

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