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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful business semantics beyond annotations, clarifying mayTellClient/clientScript and warning that draft status and proposed changes are not commitments or authorizations.

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 purpose is front-loaded, and the following sentences add specific business rules without obvious repetition. Some phrasing is clipped and could be organized more cleanly, but it is appropriately sized for the tool.

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?

An output schema and rich annotations reduce what the description must cover, and it supplies important semantic constraints. However, for a tool whose only input parameter is undocumented at the schema level, the description leaves scheduleId's meaning and format unexplained.

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?

The schema has one required parameter with 0% description coverage, and the description never mentions scheduleId, UUID format, or how to identify the schedule. It therefore fails to compensate for the missing schema documentation.

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?

States a clear verb and resource with 'Read the schedule,' and the singular reference plus required scheduleId implies retrieving one schedule rather than listing. It does not explicitly distinguish this from list_schedules or name any sibling tool, so it misses the top tier.

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?

Gives clear usage context: read the schedule before answering, quote only this record, and treat draft/proposed changes as non-authorizing. It does not name alternative tools or explicitly say when not to use this tool.

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