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 safety is covered structurally. The description adds context annotations cannot: this tool performs no in-app action ('opens nothing by itself'), returns procedural guidance, and there is no official Petpooja restaurant API. The only gap is no note on what the guidance output actually looks like in size/format.

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 ordering is sensible — purpose, then return behavior, then handoff to browser tools — but 'from ChatGPT, Claude or any AI agent' is pure filler, and the final sentence about the missing official API with a checked-on date reads as meta-justification rather than actionable guidance. Trimming those would sharpen it without losing information.

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 it returns, that it has no side effects, and what to do next. An agent has enough to call it and act on the result; only the shape/length of the returned instructions is unspecified.

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, and the description correctly implies a no-argument call by framing it as a general how-to for the user's own account. Baseline of 4 applies for a parameterless tool.

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 clarifies the actual deliverable — step-by-step instructions (screens, buttons, fields) for listing menu items rather than a returned list of items, which is important because the name suggests otherwise. It also scopes the target to the user's own Petpooja account. It stops short of naming which sibling guide tools might be the better fit.

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: this tool returns the how-to, then execution happens through the cotlet_browser_* tools in the Petpooja Cloud Browser. No explicit exclusions are given (e.g., when to prefer a direct report tool), but the handoff condition is clear.

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