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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the critical behavior that it 'opens nothing by itself' and returns instructional content rather than live data, plus the API-key constraint requiring support contact. That is real context beyond structured fields. It stops short of describing the format or length of the returned instructions.

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 message (returns steps, opens nothing, use browser tools to execute) is front-loaded, but the 'from ChatGPT, Claude or any AI agent' clause is filler and the trailing API-keys tangent is verbose. Some sentences don't fully earn their 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, read-only guide tool with no output schema, the description covers what it returns, that it performs no action, and which tools to use next. An agent has enough to call it correctly. A brief note on the shape/scope of the returned steps would make it complete.

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 are no argument semantics the description needs to compensate for, and it correctly implies no inputs are required.

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 says it will 'Get job pipeline' but then clarifies it actually 'Returns how to do it in Recruiterflow step by step (screens, buttons, fields)'. That is a specific and useful disclosure of what comes back, but the leading verb and title imply data retrieval, creating tension between name and actual behavior. An agent can eventually work out it returns instructions, but the framing is somewhat misleading.

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, and you 'then do it with the cotlet_browser_* tools in the user's Recruiterflow Cloud Browser'. It also flags the official-API alternative and why it isn't self-serve. That is clear when-to-use and how-it-pairs-with-alternatives guidance, though it doesn't distinguish among the sibling recruiterflow_* data tools.

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