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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered without description help. The description does add genuine context beyond the annotations: the result is scoped to what the caller's project is authorized to see, and writing_instruction is only present 'when the project has one'. Error behavior for unauthorized or missing experiments is not disclosed.

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 dense sentence with no filler, and the core action is front-loaded. The trailing parenthetical defining writing_instruction and the conditional clause are somewhat awkward to parse but each carries information.

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 no output schema, the description does useful work by enumerating the returned components, which is the main reason it is adequate. However, for a get-by-id tool it omits what an agent needs on the failure path (not found, not authorized) and says nothing about the required identifier.

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?

There is one parameter (experiment_id) and schema description coverage is 0%, so the description must carry the explanatory burden. It never mentions the id, its UUID form, that it is required, or how to obtain one, leaving the only input completely unqualified in prose.

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 states a specific verb (Get) and resource (a project-authorized experiment) and enumerates the payload it returns (vote aggregate, action plan, recent comments, writing_instruction). It distinguishes itself implicitly from hypotize_experiments_list by fetching a single experiment, though it never names the contrasting sibling.

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 rather than stated: an agent can infer this is the single-experiment fetch versus hypotize_experiments_list, but no explicit when-to-use, when-not-to-use, or alternative routing is given. There is also no guidance on prerequisites such as the caller needing project authorization.

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