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

Annotations already cover readOnly, idempotent, and non-destructive, and the description reinforces this with 'opens nothing by itself', which is the single most important behavioral fact for an agent that might otherwise assume a real write happened. It also discloses the output shape (step-by-step instructions) that annotations cannot express. Remaining gaps are minor, e.g. whether the steps are specific to the user's account configuration.

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 operational content is front-loaded and compact, but the final sentence about Hubstaff's REST API v2 and official read-only MCP server contributes nothing to deciding or invoking this tool and reads as filler. It could be dropped without loss.

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?

Given zero parameters, no output schema, and rich annotations, the description supplies the essential missing pieces: what is returned, that nothing is mutated, and which tools to use next. Only the handoff prerequisites (browser session state) are left implicit.

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 there is nothing for the description to disambiguate and the baseline applies. No parameter claims are made that conflict with 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 concretely that the tool returns a step-by-step guide (screens, buttons, fields) for creating a task, which is a specific and unusual output type made explicit. The name and title say 'Create task', which is misleading until the second clause clarifies nothing is actually created, but the description itself resolves that ambiguity.

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 names the follow-on tools ('cotlet_browser_*') and explains the sequence: get the guide, then perform it in the user's Hubstaff Cloud Browser. It does not state when an agent should choose this over the other Hubstaff siblings (create_project, add_time_entry) or the prerequisite that a browser session must already exist.

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