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

With readOnlyHint and destructiveHint already set, the description goes far beyond annotations by disclosing token non-disclosure, provider-specific return fields, live repository reads, dry-run writes, push permission checks, detailed failure reasons, and the null-when-unconfigured case. This is unusually rich behavioral detail.

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 purpose is front-loaded in the first sentence, and the provider-specific detail is necessary given the absence of an output schema. The dense semicolon-heavy paragraph is information-rich but could be easier to scan, keeping it just short of a 5.

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?

Because there is no output schema, the description must carry return-value documentation, and it does so thoroughly for both providers, including check outcomes, permission fields, counts, and null configuration. Nothing essential for correct invocation or interpretation appears 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 coverage is 100% for the single workspaceId parameter, and the schema already documents its fallback behavior. The description adds no syntax or format detail beyond the schema, so the 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 purpose: reporting where a workspace delivers drafts and whether a provider token exists, with provider-specific fields. It clearly distinguishes the status/configuration role, but it never acknowledges or contrasts with siblings like deliver_draft, so an agent gets no explicit routing signal.

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 explains what information is returned but gives no explicit guidance on when to call this versus alternatives such as deliver_draft or list_workspaces. 'Free to call' is a cost note, not a usage condition, so the agent must infer the appropriate context.

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