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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely useful context beyond them: it 'opens nothing by itself,' it returns procedural text, and JazzHR has no official MCP server so the API path requires a key from Settings > Integrations. That is real behavioral disclosure, though it doesn't say how the guide is formatted or whether it varies by account plan.

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 behavior is front-loaded, but the second half is a long semicolon-chained sentence mixing three ideas (no-op behavior, browser follow-up, API availability). The closing note about JazzHR's REST API and the 'checked 20 Oct 2026' timestamp is tangential to invoking this tool and could be trimmed.

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 guidance tool with annotations covering the safety profile and no output schema, the description supplies enough: what it returns, that it has no side effects, and what to do with the result. The only gap is not stating what the returned guide looks like as a payload.

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. Nothing in the schema needs elaboration, and the description correctly implies the input is implicit (the user's own JazzHR account).

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 resource (job status in the user's JazzHR account) and, crucially, clarifies what the tool actually returns: a step-by-step guide of 'screens, buttons, fields' rather than a mutation. That resolves the tension created by the imperative name. It stops short of differentiating itself from sibling jazzhr_* tools that likely behave the same way.

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 does give a next-step workflow: use the returned guide and then act with the cotlet_browser_* tools in the user's JazzHR Cloud Browser. What's missing is when to choose this over alternatives such as cotlet_app_guide or the other jazzhr_* helpers, and any preconditions (e.g., a Cloud Browser session must already be open).

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