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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, and the description's only behavioral claim ('read-only') merely restates readOnlyHint. It discloses nothing new such as pagination behavior, result ordering, or what scope of schedules is returned.

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 terse sentences, purpose front-loaded, zero filler. Nothing is redundant or padded.

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?

For a 7-parameter read tool with no output schema, the description is minimally adequate: safety profile comes from annotations and parameters from the schema. But a list tool with pagination should say whether results are paginated and how the caller learns of more pages, which is left entirely to inference.

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 the schema already documents pagination (page, page_size), auth tokens, and account_id. The description adds no parameter meaning beyond that, which matches the baseline 3 for fully covered schemas.

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?

Names a specific verb and resource ('Lists schedules') and even cites the underlying endpoint GET /schedules/. However, it does nothing to distinguish itself from the dozens of sibling list_* tools or from get_schedule, so an agent must infer the list-vs-single distinction from the plural noun alone.

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?

There is no statement of when to use this versus get_schedule (single schedule), list_user_schedule, or assign_users_to_schedule. 'Limitations: read-only' is a constraint, not usage guidance; no exclusions or alternatives are offered.

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