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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond that: it costs nothing and consumes no browser session, and it works for uncatalogued apps. It stops short of saying whether results are cached or how large the returned guide typically is.

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 second sentence is a long comma-chained enumeration of guide contents that is hard to parse on first read, and the trailing list of covered Sprout Social actions is dense. The trigger sentence is well placed, but the middle of the description is sprawling rather than front-loaded.

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 output schema, the description does the work of telling the agent roughly what comes back: browser choice, sign-in link, method, screens, menus, actions, notes, and dedicated tools. That is sufficient for a read-only reference tool, though it omits how the guide is scoped by the task parameter.

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?

Schema description coverage is 100%, so both parameters (app with its default of Sprout Social, and task) are already documented in the schema. The description alludes to workspace-specific browser choice and to app-specific actions but adds no format or usage nuance beyond the schema, so baseline 3 applies.

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 concrete purpose: retrieving a per-app playbook covering which browser to use, the sign-in link, a step-by-step method, screens/menus/actions, and dedicated tools. It distinguishes itself from the browser_* siblings by being the prerequisite reference call, though the opening sentence is a comma-run that buries the core verb rather than front-loading it.

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 trigger: "Call it before the first browser step in an app," and clarifies the fallback that an app outside the catalog still gets the general method. It does not name when to skip it (e.g., if the guide was already retrieved this session) or contrast it with cotlet_apps for discovering apps.

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