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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered; the description adds what those annotations cannot — the two return artifacts (view link, edit link) and the error-list-then-retry loop. The only residual tension is the 'make a page' framing against readOnlyHint=true, but the description makes clear output is links rather than a mutated stored resource, so it reads as a rendered/idempotent transformation rather than a contradiction.

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 core action, then returns, then the trigger list, then the prerequisite and retry instructions — a sensible order with no filler sentences. The enumeration of schedule types is long but earns its place as retrieval surface for user phrasings.

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 single-parameter tool with no output schema, the description supplies exactly what is missing elsewhere: the shape of the return (view link, edit link, error list) and the corrective loop on failure. Nothing an agent needs to call it or recover from a bad call is absent.

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?

With one parameter at 100% schema coverage, the baseline is 3; the description goes further by naming the 'Schedule Gizmo text' format and pointing to get_format_guide for syntax, which is the main practical obstacle to filling that parameter correctly.

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 specific transformation verb and resource: turn Schedule Gizmo text into a finished one-page schedule. It also distinguishes itself from the sibling it names (get_format_guide) by role, so an agent can route between them without inspecting either 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?

Gives an explicit trigger list (rota, shift pattern, agenda, lineup, planner, calendar), a prerequisite alternative (use get_format_guide first if unsure of the format), and a follow-up rule (fix errors and call again). It covers when to use, what to do before, and what to do after — nothing is left to inference.

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