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

Annotations already declare readOnly/idempotent/non-destructive, and the description confirms the tool performs no action of its own and only yields a procedural guide. It also discloses that DINGG publishes no public API, keys, or developer docs — a constraint the agent needs in order to not look for a REST route. This is substantive context beyond the annotation set.

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-loaded with the core behavior and the non-execution caveat, then the follow-up tools, then the API constraint. The 'from ChatGPT, Claude or any AI agent' clause and the dated API-check note are slightly padded but still carry information an agent may need.

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 parameters and no output schema, the description covers what matters: what the tool returns (a step-by-step procedure), that it mutates nothing, and which tools finish the job. It does not address preconditions such as the user being signed in to DINGG or what happens if the account is not connected, which would be useful for a browser-driven workflow.

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 schema is trivially complete. Baseline 4 applies; no parameter-level gaps exist.

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 uses a concrete verb and resource: it returns step-by-step in-app instructions (screens, buttons, fields) for booking an appointment in the user's DINGG account. It explicitly negates the implication of the name by stating it 'opens nothing by itself', which keeps an agent from expecting an executed booking. It stops short of naming the DINGG siblings (find_free_slots, reschedule_appointment), so differentiation is only at the class level (guide vs. browser action).

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 usage path: call this first to obtain the procedure, then carry it out with the cotlet_browser_* tools in the DINGG Cloud Browser. It does not state exclusions, e.g. that rescheduling goes to dingg_reschedule_appointment or that slot discovery goes to dingg_find_free_slots, leaving a gap in sibling routing.

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