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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The only added behavior is the passing hint that pending suggestions can be included, but pagination/cursor semantics, default limit, and filter interactions are unmentioned.

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?

A single short sentence is front-loaded with no filler, but at this length it reads as under-specification rather than efficient concision given the tool's parameter richness.

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?

With 7 parameters at 0% schema description coverage, no output schema, and a list operation whose pagination contract is undocumented, the description does far too little to prepare an agent to call it correctly. It omits what the response contains and how to page through results.

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% across 7 parameters, including a required workspace and filters like funnel, status, and target_path that have no explanation anywhere. The description only faintly gestures at include_suggestions and says nothing about limit/cursor usage or the status enum.

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 says "Read experiments and pending suggestions," which identifies the resource but uses a vague verb ("read") where the tool actually lists with pagination. It does not distinguish this tool from siblings like abtests_get or abtests_prepare, so an agent can only infer listing behavior from the name suffix.

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?

There is no statement of when to use this tool versus abtests_get (single fetch) or abtests_prepare. No context on filtering needs, pagination, or prerequisites is given, leaving the agent to infer usage from the name alone.

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