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

Annotations already declare this a safe, non-destructive, non-open-world read, so the safety profile is covered. The description adds the shape of what comes back (id, target, created, name count, status), which is useful, but says nothing about ordering, pagination, or empty-result behavior for a list operation.

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 sentences with zero filler; the scope of the operation is front-loaded before the return columns. Every clause carries information the agent can act on.

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 list tool with no output schema, the description supplies both the scoping rule and the returned columns, which is most of what an agent needs. The only real gap is list behavior (ordering, pagination) and the boundary with get_brand_names.

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 100%, so the single researchId parameter is fully documented as 'The research ID whose brand-name runs to list'. The description restates the parent-scoping idea but adds no format or constraint detail beyond the schema, making the baseline 3 appropriate.

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 (List) and resource (brand-name runs) scoped to a parent research, and clarifies the one-to-many relationship ('a research can hold several'). It does not explicitly distinguish itself from the sibling get_brand_names, which is the main ambiguity an agent would face.

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 by 'for a specific research' rather than stated as a condition. There is no mention of when to use this versus get_brand_names or create_brand_names, nor any prerequisites, so the agent must infer routing from names alone.

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