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

Annotations already declare readOnly, idempotent and non-destructive, so the description earns credit by adding what the schema and annotations do not: the returned scope (experiment + policy + latest 500 recovery records) and the preconditions (authenticated native buyer, existing funded placement). It does not discuss pagination or error behavior.

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 tight sentences with the read scope front-loaded; nothing is padded. The trailing sentence about the authenticated buyer and funded placement is slightly jargon-heavy but does carry real context.

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?

For a one-parameter, read-only tool with no output schema, the description usefully sketches what is returned and the implicit 500-record bound. Only pagination and failure modes are left unaddressed, which is minor at this 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?

Schema coverage is 100% and the single parameter already documents itself as a native experiment ID sourced from create_creative_experiment. The description adds no format or constraint detail beyond that, so the baseline of 3 applies.

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 read verb and enumerates the resource set it returns: the native experiment, its policy, and the latest 500 owned creative recovery records. That is far more informative than the name alone, though it never explicitly distinguishes itself from create_creative_experiment or stop_creative_experiment.

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?

Usage is only implied by 'Read your native experiment', and the schema's note that the ID comes from create_creative_experiment hints at a workflow. There is no explicit when-to-use statement or named alternative among the closely-named siblings.

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