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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this in plain language by saying the tool 'opens nothing by itself' and only returns guidance. It also discloses the dependency on cotlet_browser_* tools and explains why no API route exists, which is real context beyond the structured fields. It still does not say what the returned guidance looks like structurally or how long or detailed it is.

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 definition is front-loaded: it first explains what the tool returns, then what to do next. The closing sentence on 404s at ezlawnbiller.com/api, /developers and /docs is somewhat verbose, but it justifies the browser-based workaround rather than an API call, so it still earns most of its place.

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 zero-parameter guidance tool with no output schema, the description covers what is returned (screens, buttons, fields), that nothing is executed, and which tools complete the job. The only gap is the shape of the return value, which matters little given the annotations already establish a safe read-only operation.

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 tool takes zero parameters, so the baseline expectation is a 4. The description correctly implies no input is required: it acts on the implicit current draft in the user's own account and adds no parameter meaning because none exists.

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 precisely what the tool does: it returns step-by-step instructions for applying a draft to LIVE rather than performing the action ('opens nothing by itself'). The verb-plus-resource pairing is clear, though the tool's name ('apply_draft_to_live') could mislead an agent into thinking it is the write operation itself, and the description does not distinguish it from siblings such as return_to_live or apply_to_all_weeks.

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 says what to do afterwards ('then do it with the cotlet_browser_* tools in the user's EZ Lawn Biller Cloud Browser'), which is a useful next-step pointer, but it never states when to use this tool versus the other draft or LIVE siblings. Usage is only implied by context, so there are no explicit exclusions.

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