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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value the annotations don't: it names the fields the records contain, which matters because there is no output schema. It does not mention result size or pagination, the one behavioural gap.

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 dense sentences with zero filler: the payload description comes first, the filtering options second. Nothing repeats the tool name or the annotations, and every clause adds new 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?

For a zero-required-parameter, flat-schema list tool with no output schema, the description supplies both the return shape and the filter vocabulary, which is what an agent needs to call it correctly. Only pagination/result-size behaviour is left implicit.

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% and neither parameter declares an enum, so the description carries the full burden — and it delivers by spelling out the accepted values (cluster: a2a | space | energy-data; status: live | pilot | lab | programme | data-capability | waitlist). It does not state case sensitivity or matching behaviour, but the critical closed value sets are there.

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?

Opens with a specific verb+resource ('The venture registry: every GBC venture') and enumerates exactly what each record carries (cluster, status, buyer, pricing, URL, agent access). The only friction is the undefined acronym 'GBC', which an agent outside the org cannot resolve, but the scope is otherwise unmistakable and none of the siblings (network_stats, skill_rank, solar_prefeasibility) overlap with it.

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?

Makes the default behaviour explicit — it returns *every* venture unless you narrow with the optional cluster or status filter — which is the key when-to-use decision for this tool. There are no exclusions or named alternatives, but the siblings are unrelated domains, so there is nothing to route against.

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