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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description goes further by describing the return payload (screens, buttons, fields) and explicitly stating it 'opens nothing by itself,' which prevents an agent from assuming the publish already happened. With no output schema, that disclosure is the only source of return-format information.

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 behavior is front-loaded and unambiguous, but the closing sentence on Connecteam's official API and MCP server runs long and includes a dated verification note that adds bulk beyond what an agent needs to select and call the tool. It earns partial place by blocking a plausible wrong path, yet could be one clause instead of three.

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, read-only instruction tool with no output schema, the description covers everything an agent needs: what it returns, that it performs no action, and which tools to use next. Annotations handle the safety profile, so no material gaps remain.

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 no parameters, so the description has nothing to disambiguate at the schema level; a 4 baseline applies. The implicit point that the target account is the user's own is useful scope information even though no argument encodes it.

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 ('Publish shifts in the user's own Connecteam account') and immediately disambiguates what the tool actually does: it returns a step-by-step guide rather than performing the publish. That distinction separates it from the cotlet_browser_* tools it hands off to.

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?

Gives clear sequencing guidance ('then do it with the cotlet_browser_* tools') and preempts the obvious alternative by explaining that Connecteam's API needs the Expert plan and its official MCP server cannot act on the account. It does not say when this tool is the wrong choice among the sibling Connecteam action tools, but the resource name makes that largely self-evident.

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