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

The description adds only two behavioral notes: that no supplier request is triggered, and that ad visibility is not proof of conversions. It says nothing about the side effects implied by the supplied annotations (destructiveHint=true, openWorldHint=true, readOnlyHint=false), such as what session or catalog state a 'read' may mutate. For a tool whose annotations declare it destructive, this leaves the safety profile unexplained and slightly at odds with the 'Read' framing.

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?

Three short sentences with the core action front-loaded and no filler. The final 'Ad visibility' caution is tangential to invocation but is a legitimate interpretation warning, so it earns its place more than most trailing sentences.

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 not be described, and the read/no-supplier-request distinction is captured. Still, for a tool with nested objects and required contract parameters (read_skills proofs, catalog version, request key), the description omits the prerequisite chain that a caller must satisfy, leaving a significant gap against tool complexity.

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?

Six parameters, five required, with only 50% schema description coverage; the description mentions none of them. It never explains the role of work_id, request_key, read_skills, or the arguments.saved/run_id sub-object, so it does not compensate for the undocumented half of the schema. High-coverage parameters like expected_catalog_version and publication_proposal_id are already handled in the schema itself, which keeps this at the baseline rather than lower.

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 and resource combination ('Read saved research and current request status') and scopes it to 'this studio'. It does not name the sibling tools it must be distinguished from (native.start_social_research, native.wait_for_social_research, native.quote_social_research), so an agent still has to infer the boundary, but the core purpose is unambiguous.

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?

'Does not make supplier requests' implicitly separates this read from the research-starting siblings, which is useful routing signal. However, there is no explicit statement of when to call this versus native.wait_for_social_research for status polling or native.read_work for the parent work item, and no prerequisites or exclusions are given.

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