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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the return value is procedural guidance (screens, buttons, fields) and the tool performs no mutation, which is exactly what an agent needs to know before deciding to chain it with browser tools.

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?

Three sentences, front-loaded with the action and immediately qualified by the read-only nature, which is the right order. The phrase 'from ChatGPT, Claude or any AI agent' is filler, and the API-documentation note is only marginally relevant context, keeping it below a 5.

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, no-output-schema guidance tool with rich annotations, the description covers purpose, return format and the required follow-up tool family. It could note prerequisites (being logged into Petpooja) but nothing essential to correct invocation is missing.

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 and the baseline of 4 applies. It correctly implies no input is required to obtain the guidance.

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 (switch outlet online) and then immediately clarifies the tool's actual function: it returns step-by-step instructions rather than performing the switch. The clause 'opens nothing by itself' plus the handoff to cotlet_browser_* tools makes it unmistakable against siblings like petpooja_switch_item_off_online.

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 states the usage pattern explicitly: call this to get the screens/buttons/fields, then execute with cotlet_browser_* in the Petpooja Cloud Browser. That is a clear when-to-use plus a named alternative family. It does not spell out exclusions (e.g. what to do if the outlet is already online or the session is not authenticated), so it stops short of a 5.

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