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 behavioral context: it returns screens/buttons/fields guidance and performs no action itself, and it notes the official API is read-only. It does not explain the shape of the returned guidance beyond that summary, so it is helpful but not rich.

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 read-then-act split is front-loaded and useful, but the second sentence is long and clause-chained, and the closing sentence about the read-only OData API and its check date is tangential to calling 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?

For a zero-parameter tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields) and how to proceed afterward. It omits how the target appointment is specified or scoped, which is a meaningful gap for an update-oriented tool.

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?

With zero parameters the baseline is 4. The description correctly implies no inputs are required to obtain the guidance, though it never says how the specific appointment to update is identified, which is the one semantic gap.

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 gives a specific verb and resource ('Update appointment in the user's own MarketSharp account') and clarifies it is invoked from AI agents. It does not explicitly distinguish itself from siblings such as marketsharp_create_lead or marketsharp_get_contract_status, but the verb+resource pairing is unambiguous.

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 clearly says the tool returns step-by-step instructions and that the actual update is done with cotlet_browser_* tools in the Cloud Browser, plus that the tool 'opens nothing by itself'. That is a clear use context, but there are no explicit when-not conditions or prerequisites beyond the user owning a MarketSharp account.

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