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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious domain behavior: Ideas are experiments in the Idea status rather than a separate object, and Testing/Analysis are legacy aliases of Running/Analyzing. It omits result ordering and pagination behavior, which keeps it from a 5.

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 compact sentences, front-loaded with the core operation, followed by only the disambiguating domain notes that an agent cannot get from the schema. No filler.

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 seven parameters, no output schema, and zero schema description coverage, the definition should at minimum explain the filter parameters and cursor-based pagination. It covers the status-naming pitfall well but leaves the filtering and paging model entirely to inference.

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%, so the description must carry the burden. It partially does: the note that Testing and Analysis are legacy names directly explains the statuses enum values and warns the agent it may need to filter on either spelling. However, tags, funnel, updated_after, limit and cursor receive no semantic explanation at all.

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 verb and resource with scope: 'List the project-scoped experiment backlog and pipeline'. It also clarifies that Ideas are included, which preempts a likely misreading. It stops short of naming sibling tools like hypotize_experiment_get for single-record retrieval, which is the one remaining differentiation gap.

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 implied: this is the tool for enumerating experiments within a project. There is no explicit statement of when to prefer it over hypotize_experiment_get or hypotize_learnings_list, and no guidance on paging through results; the agent must infer that from the schema.

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