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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully discloses the shape of each returned record (sector, passage counts, AI-tool flag), but says nothing about result size, ordering, or pagination for what could be a large archive-wide list.

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?

One front-loaded sentence with no filler; the scope statement comes first and the returned fields follow. Nothing unnecessary is present.

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 earns credit for naming the returned fields, which an agent otherwise could not know. The main residual gap is enumeration behavior (ordering, pagination, volume) for an archive-wide listing, but the core call semantics are covered.

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 coverage is 100% and the single ai_vendor parameter is fully documented, so the schema does the heavy lifting. The description's phrase 'whether it sells AI tools' echoes the schema's filter semantics without adding format or default behavior beyond it, making 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?

The description names the resource ('Every organization in the archive') and the fields returned ('sector, passage counts and whether it sells AI tools'), which distinguishes it from the singular get_organization sibling. The verb 'list' is only implicit (carried by the title), so it is clear but not maximally explicit.

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: enumerate every organization when you need a full inventory. There is no explicit when-to-use/when-not guidance, no mention of when to prefer search_passages or get_organization instead, and no note on expected volume or filtering strategy.

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