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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it specifies the return type (a step-by-step guide with screens, buttons and fields) and states it 'opens nothing by itself', explaining the two-step handoff to the browser tools. It does not describe the guide's size or format.

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 two sentences are front-loaded and useful: what it returns and that it acts on nothing. The final sentence about Hubstaff's REST API v2 scopes and a read-only official MCP server (checked 17 Oct 2026) does not help an agent decide to call or invoke this tool, and adds length without function.

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?

With no input parameters and no output schema, the description carries the burden of explaining the return value, which it does by naming the step-by-step guide contents. Combined with the explicit follow-up via cotlet_browser_* tools, an agent has enough to act correctly. The only omission is any hint of what the response looks like in structure or how large it may be.

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 no parameter semantics to compensate for and the baseline of 4 applies. The description correctly implies the call needs no input because everything is derived from the user's own Hubstaff 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 states a concrete outcome: it returns step-by-step instructions (screens, buttons, fields) for adding a time entry in Hubstaff, and explicitly says it performs no action itself. This resolves the tension created by the tool name 'add time entry' versus a read-only behavior. It does not, however, differentiate itself from the other hubstaff_* siblings such as hubstaff_review_manual_time_request or hubstaff_approve_timesheet.

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 a clear workflow: fetch the guide here, then execute it with the cotlet_browser_* tools in the user's Hubstaff Cloud Browser. That is genuine usage context. It stops short of exclusions — nothing says when this tool is the wrong choice versus other Hubstaff tools or versus a direct API call, and the trailing note about Hubstaff's official API is informational rather than routing.

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