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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', so the safety profile is unambiguous. It adds context beyond the annotations: the returned payload is a procedure, and the API note explains that SingleOps exposes only a Lead Entry API with no general-purpose read/write API and no native Zapier integration, which matters for an agent deciding whether to attempt a direct API path.

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 information is front-loaded, but the trailing API note is garbled, with nested quotes and a dangling colon ('SingleOps's official API: SingleOps has a Lead Entry API only: "It is not a general-purpose job-creation or read/write API..."'). That passage is longer than needed and reads awkwardly, costing clarity.

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, no output schema and annotations already covering safety, the description supplies what an agent needs: what it returns, that it performs no side effects, and which tools to use next. It could be more explicit that the response is instructional text rather than a created record, but overall it is complete for a zero-parameter guidance 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no inputs are needed because it only returns instructions.

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 specific resource and, crucially, what the tool actually returns: step-by-step SingleOps instructions covering screens, buttons and fields. It also names the follow-on tools (cotlet_browser_*), which separates it from the list/schedule siblings. The opening phrase 'Create lead in the user's own SingleOps account' sits in tension with 'opens nothing by itself', so an agent skimming only the first clause could misread it as a mutating tool.

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 clear context for use: call this to get the procedure, then execute it with the cotlet_browser_* tools in the SingleOps Cloud Browser. It does not state when NOT to use it (e.g. versus the browser tools alone), but the sequencing guidance is explicit enough to route an agent.

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