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

Beyond the readOnly/idempotent/destructive annotations, the description discloses what the return payload contains (request, assistant message, one to three changes with target/current/proposed replacement) and explicitly states that nothing is applied until the decide tool is called. This is rich, non-obvious behavioral context that annotations do not provide.

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?

Every sentence earns its place: the first states the core behavior and null case, the second summarizes the payload structure, and the third clarifies the lack of side effects. The most decision-relevant information is front-loaded, and there is no redundant filler.

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 present, the description takes on the burden of explaining the return value and does so well: null vs. a structured payload and the key fields an agent needs to review. It also clarifies the side-effect boundary. For a simple one-parameter read tool, nothing important 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% and the single workspaceId parameter is already documented ('Defaults to the API key's workspace'). The tool description adds no parameter-specific meaning, but it also does not need to because the schema is sufficient. 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?

The description states a specific action ('Get'), the exact resource ('the workspace's pending playbook proposal'), and the null-when-empty behavior. It clearly distinguishes this from general playbook tools like campaignstack_get_playbook by focusing on the pending proposal awaiting decision.

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?

The description gives clear context: this is for retrieving a proposal that is waiting for a decision. It references campaignstack_decide_playbook_proposal as the follow-up action, making the tool's place in the workflow obvious. It does not explicitly list exclusions or compare itself to get_playbook, so it stops short of a perfect 5.

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