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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful context beyond them: no action is taken, nothing is opened, and the return value is a step-by-step screen/button/field walkthrough. The closing sentence about Invoice Ninja's REST API and token creation is unrelated to this tool's behavior and adds no transparency value.

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 opening clause buries the actual behavior behind an action-sounding verb, and the final sentence about Invoice Ninja having a REST API (with a date stamp) is filler that does not describe this tool. Only the middle clause about returning steps and opening nothing earns its place, so the definition is noisy relative to its informational content.

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?

With no output schema and no parameters, the description must explain what comes back, and it does reasonably well by naming the step-by-step format and the follow-up browser tools. What is missing is an explicit statement that this tool creates nothing itself, plus guidance on how it relates to cotlet_app_guide and invoice_ninja_create_invoice, which leaves the read-only/create confusion only partly resolved.

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; the 100% empty schema is the correct baseline. No parameter claims are made or contradicted.

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 does convey the real behavior ("Returns how to do it in Invoice Ninja step by step (screens, buttons, fields) and opens nothing by itself"), which is important given the name says "create quote". But it leads with "Create quote in the user's own Invoice Ninja account," which reads as an action tool, and it never distinguishes itself from siblings like invoice_ninja_create_invoice or cotlet_app_guide. An agent has to read the whole thing to learn this tool produces instructions, not a quote.

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 explicitly routes the agent forward: "then do it with the cotlet_browser_* tools in the user's Invoice Ninja Cloud Browser," which tells the agent this is a preparatory step in a two-phase flow. It does not state when to prefer this over cotlet_app_guide, nor any exclusion conditions, so it stops short of full when/when-not guidance.

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