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

Annotations already cover the read-only/idempotent safety profile, and the description goes well beyond them with interpretive semantics the schema cannot carry: PROCESSING means reporting is still being finalized, no status-transition timestamp exists, the scheduled date is not a delay diagnostic, and null rates mean unavailable rather than zero. That directly prevents the most likely agent misreadings.

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?

Purpose is front-loaded in the first sentence, and the remaining three sentences are dense caveats with no filler. The trailing caveat cluster is slightly compressed and could be split for readability, but nothing is wasted.

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 annotations handle safety; the description covers the non-obvious result semantics thoroughly. What is missing is only the meaning of the two required identifiers, which leaves a small gap for a two-parameter tool.

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 0% and both parameters are required, so the description carries the full burden. It never mentions organization_id at all and only obliquely implies campaign_id via 'one simulation campaign'; the agent must infer that organization_id is the owning-org scoping key.

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?

Specific verb and resource with scope: 'Read privacy-safe outcomes, rates, timings, score, and schedule for one simulation campaign.' The phrase 'one simulation campaign' distinguishes it from the sibling search_campaigns, and the enumerated payload fields tell the agent exactly what comes back.

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: 'one simulation campaign' suggests a per-campaign detail lookup versus search_campaigns, but the description never states when to call this instead of get_organization_overview or search_campaigns, nor any prerequisite for obtaining campaign_id. There are no exclusions or alternative routing.

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