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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope; the description reinforces this with 'opens nothing by itself', which is the key behavioral fact an agent needs. It also adds an external-dependency caveat about API/MCP limitations. The dated verification stamp ('checked 28 Oct 2026') is extraneous but not harmful.

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 is front-loaded in the first two clauses, but the second half drifts into an API-availability tangent with a hard-coded date that doesn't help the agent decide or act. Tighter phrasing would keep the browser-tool handoff and drop the audit-style note.

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 guide-generation tool with no output schema, the description covers what it returns (screens, buttons, fields), what it does not do (opens nothing), and the follow-up execution path. Complete enough to invoke correctly.

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 and the baseline applies. Nothing in the description misleads about inputs.

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 and resource ('Reschedule inspection in the user's own Spectora account') and then immediately clarifies what the tool actually does: returns step-by-step Spectora instructions rather than performing the action. The name/behavior gap is disclosed, so an agent won't mistake it for a mutation tool, though the naming still creates a small initial mismatch.

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 routes the agent: use this to get instructions, then execute with the cotlet_browser_* tools in the Spectora Cloud Browser. It also preempts the obvious alternative (the official Spectora API and its read-only MCP server) by noting neither supports scheduling. Lacks an explicit 'when not to use' beyond that.

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