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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still earns credit for two non-obvious disclosures: the tool opens nothing by itself and returns a procedural recipe, plus the plan restriction on Slab's official GraphQL API. It omits prerequisites such as whether the Slab app must be connected or the user logged in, which matters for a browser-driven flow.

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 behavior-carrying sentences come first, which is good, but the opening 'from ChatGPT, Claude or any AI agent' is promotional filler and the parenthetical '(checked 28 Oct 2026)' reads like provenance rather than agent-useful information. The middle clause about step-by-step returns is workable but wordy.

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 whose output is a guide, the definition covers what comes back and how to chain into the browser tools. It does not address the obvious question the agent will have, given no post identifier: how the target post is determined, or what happens if the Slab app or session is not already available.

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 of 4 applies. The description does not need to compensate for any schema 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?

States a specific verb and resource ('Read post in the user's own Slab account') and then immediately clarifies the actual behavior: it returns step-by-step instructions rather than post content, and opens nothing itself. That clarification prevents the most likely misread of the name, though it never distinguishes this from nearby siblings such as slab_get_post_insights, slab_verify_post, or the generic cotlet_app_guide.

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 an explicit usage path: call this to get instructions, then carry them out with the cotlet_browser_* tools in the user's Slab Cloud Browser. Clear about the follow-up step, but offers no when-not guidance and does not say how this differs from the generic app-guide or browser read alternatives.

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