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

Annotations already supply readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds two useful pieces of context beyond that: the run must be "authorized" and the draft should not be auto-persisted, but it says nothing about pagination, freshness, or what happens when the run is incomplete.

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?

Two short sentences, zero filler, with the read operation stated before the follow-up consumer instruction. It is appropriately sized for a simple lookup; the only minor cost is that the second sentence mixes behavioral guidance into what reads like a purpose statement.

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?

An output schema exists, so return values need no prose, and the description correctly points at the draft business profile. What is missing is the anchor for the two required IDs and any link to the sibling that creates the run, which an agent needs in order to sequence calls correctly.

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?

Coverage is 50% and the only schema text is the useless "UUID string."; workspaceId has no description at all. The description refers to "one authorized website extraction run" but never explains what runId identifies, what workspaceId scopes, or where either value is obtained (e.g., from workspace_brand_scan output).

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 names a specific verb (Read) and a specific resource (one authorized website extraction run plus its draft business profile), which is far more than a restatement of the name. It stops short of naming the sibling that produces the run (workspace_brand_scan), so the read-vs-create relationship must be inferred from the name pair.

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?

"Show the extracted fields to the user for review before saving them as defaults" implies the intended place in the workflow (retrieve draft, human reviews, then persist). However, it never says when to call this versus workspace_brand_scan or workspace_context_get/save, and gives no prerequisites such as the run needing to have finished.

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