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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral details beyond annotations: returns null if the workspace does not exist, an unwritten playbook comes back as an empty object, and explains the injection context of each section (every message, first messages, replies). This is strong added value.

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 description is dense but every sentence earns its place: it lists the return structure, provides usage context, states edge cases, and names the sibling tool to use for creation/refresh. The structure is efficient, with front-loaded purpose followed by valuable behavioral and routing details.

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?

There is no output schema, so the description carries the full burden of explaining the return value. It thoroughly enumerates all returned fields, their semantic meaning, and their injection contexts. It also covers null and empty-object cases and directs the agent to the correct mutation/creation sibling. Nothing critical is missing.

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% for the single optional workspaceId parameter, which already states 'Defaults to the API key's workspace'. The description does not add parameter-level detail, but it also does not need to because the schema fully documents the parameter. Baseline 3 is appropriate.

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 ('Get the workspace's playbook') and details exactly what is returned: playbookSections with individual fields, offerContext, and capabilities. It clearly distinguishes this from related siblings like campaignstack_regenerate_playbook and campaignstack_update_workspace.

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?

Explicitly tells the agent when not to use this tool: 'Use campaignstack_regenerate_playbook to create or refresh it' and notes that all returned elements are editable via campaignstack_update_workspace. This provides clear direction for when to call this versus alternative tools.

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