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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by stating explicitly that the tool 'opens nothing by itself' and returns instructions only, plus the MYOB API access obstacles that motivate the browser-automation route. It stops short of describing the shape or length of the returned instructions.

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 most important fact — that the tool returns instructions instead of creating anything — is buried mid-sentence after a misleading opener. The closing paragraph on MYOB's REST API, OAuth consent and app registration is informative but long and secondary for a zero-parameter read-only tool, diluting the core message.

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, read-only, closed-world tool with no output schema, the description covers what comes back ('step by step screens, buttons, fields') and what the agent should do next. The residual gap is that with no output schema, more detail on the returned instruction format or any failure modes would help, but the essentials are present.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no input is required, since the target bill details must be supplied elsewhere.

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 names a specific verb and resource (create a bill in the user's MYOB account) and immediately clarifies the actual deliverable: a step-by-step guide of screens, buttons and fields rather than a performed action. That distinction is important and is stated plainly, but the opening framing ('Create bill...') initially reads as a write operation, and it never distinguishes this from the sibling myob_create_invoice.

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 a clear usage path: call this to get MYOB instructions, then execute them with the cotlet_browser_* tools, which is an explicit handoff to the correct downstream tool family. It also explains why the official MYOB REST API is not a viable alternative (approval form, app registration, per-company-file OAuth consent). It does not name or exclude the sibling invoice/payment tools, so exclusion guidance is absent.

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