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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces this usefully with 'opens nothing by itself,' clarifying that the tool produces guidance rather than sending anything. However, the closing sentence about Alegra's official REST API is unrelated to this tool's behavior and adds confusion rather than transparency.

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 core is two tight clauses that front-load the purpose and the non-execution caveat. But 'from ChatGPT, Claude or any AI agent' is filler and the trailing REST API sentence does not help an agent select or invoke this tool, so it does not earn 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 does the necessary work: it says what is returned (steps with screens, buttons and fields) and how to continue afterwards. The dangling API remark is the only element that leaves an agent with an unresolved question.

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, which establishes the baseline of 4. The description correctly implies no input is needed while making clear the returned content is the substantive output.

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?

Despite a name that implies an action ('email invoice'), the description states precisely what the tool returns: step-by-step Alegra instructions covering screens, buttons and fields, and it explicitly says it 'opens nothing by itself.' It also distinguishes itself from the execution layer by naming cotlet_browser_* as the follow-up. The only weakness is that it doesn't differentiate from the other alegra_* siblings.

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?

Clear usage context: call this to obtain the procedure, then carry it out with cotlet_browser_* tools in the Alegra Cloud Browser. That is an explicit handoff to an alternative. It lacks any when-not-to-use condition or guidance for cases where the official REST API would be preferable.

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