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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this by stating it 'opens nothing by itself', resolving the misleading 'add_lead' name. It also discloses the important external constraint that Studio Ninja has no public API, webhooks or Zapier app, explaining why browser automation is required. It adds no return-format or freshness caveats beyond the oddly specific 'checked 8 Nov 2026' date note.

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 purpose and the key behavioral caveat, then the operational next step. The closing integration/partner sentence is partly background justification rather than action-guiding, so it is slightly padded but still earns its place by explaining the browser-tool dependency.

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 a full annotation set and no output schema, the agent learns what it returns, that it performs no actions, and which tools to chain afterwards. The only gap is that the specific content of the returned steps (what screens/fields are covered) is described generically.

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 the schema carries the full parameter burden and there is nothing for the description to compensate for. Baseline 4 applies; the description correctly avoids inventing parameter discussion.

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 specifies the resource (Studio Ninja leads) and, crucially, the actual output: step-by-step instructions with screens, buttons and fields. The opening phrase 'Add lead in the user's own Studio Ninja account' momentarily reads like a write action, but the second sentence disambiguates it as a guidance tool. It does not explicitly contrast itself with cotlet_app_guide, so it stops short of a 5.

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 clear when-to-use context (user wants to add a lead) and an explicit follow-up path: use the cotlet_browser_* tools in the Studio Ninja Cloud Browser to actually perform the steps. No when-not-to-use guidance or explicit alternative among the studio_ninja_* siblings is named, which keeps it below 5.

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