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

Annotations already declare readOnlyHint=true, destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which is valuable confirmation that no side effect occurs. It also discloses the return shape (screens, buttons, fields of a step-by-step walkthrough), going beyond the annotations. The API/MCP remark adds little behavioral value for invocation.

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?

Front-loads the action and the key fact that nothing is executed, which is the most important information for an agent. The closing sentence about Timetastic's REST API and lack of an official MCP server, including a dated check, is interesting but does not help an agent select or invoke this tool.

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 what comes back, and it does: a step-by-step guide with screens, buttons, and fields. It also names the follow-up tools needed to actually complete the decline, so an agent has a coherent end-to-end path.

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 explain; baseline applies. The description does not falsely imply any inputs are needed, keeping expectations aligned 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?

States a specific verb (decline) and resource (leave request) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the decline itself. The verb 'decline' also implicitly separates it from the sibling timetastic_approve_leave_request, though that contrast is never made explicit.

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?

Explicitly tells the agent what to do next: 'then do it with the cotlet_browser_* tools in the user's Timetastic Cloud Browser', which is a clear hand-off rule. It lacks an explicit statement of when not to use it (e.g., versus approving or versus reading pending requests), so it stops short of full routing guidance.

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