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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with that by emphasizing it opens nothing by itself. It adds genuinely useful context beyond the annotations: the return is procedural guidance (screens, buttons, fields) and the API is only available on the top plan. It stops short of describing the guide's format or failure modes if no browser session exists.

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 core purpose and the key caveat that it performs no action. The API-plan note is somewhat tangential and the middle sentence is dense, but every sentence carries actionable information for the caller.

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, non-mutating guidance tool with full annotation coverage and no output schema, the description supplies what an agent needs: what is returned, that nothing is executed, and which tools to chain next. Minor gaps remain around session prerequisites and whether a Manatal tab must already be open.

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 baseline is 4; there is nothing for the description to disambiguate. The description's mention of 'with reason' hints at the domain concept but does not imply any input the caller must supply, which matches the empty schema.

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 states a specific verb+resource (drop a candidate with a reason in Manatal) and, crucially, clarifies the deliverable is a step-by-step how-to rather than an executed action. It distinguishes itself from action-performing siblings by saying it 'opens nothing by itself' and that execution happens via cotlet_browser_* tools. Slight ambiguity remains because the name alone reads like a mutating operation on Manatal.

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 workflow context: call this to get the Manatal screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the user's Cloud Browser. It also notes official API availability is plan-gated, which implicitly explains why a browser path is offered. It does not state explicit exclusions or prerequisites such as needing an already-open Manatal tab.

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