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

No annotations are provided, so the description carries the disclosure burden. It compensates by enumerating the returned fields (key, label, type, required, help text, options) and showing how the output feeds submit_enquiry, but says nothing about read-only nature, permissions, or caching/rate behavior.

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, zero filler. The return contents come first and the chaining instruction to submit_enquiry comes last, which is exactly the right front-loading.

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 and no annotations, the description must describe the return payload, and it does so field by field. It also ties the output to the downstream submit_enquiry call, leaving only the sibling distinction to enquiry_describe unaddressed.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for 0 params is 4. The mention of 'field key' correctly refers to the return shape rather than an input argument.

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 precisely what the tool returns - every field of the BioBricks enquiry with key, label, type, required flag, help text and allowed options. An agent knows the resource and the payload shape, but the description never differentiates itself from the sibling enquiry_describe, which plausibly overlaps.

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?

It gives one concrete workflow cue - pass answers to submit_enquiry keyed by field key - which is genuinely useful routing advice. It does not say when to call this versus enquiry_describe, nor any prerequisite, so usage is only partially covered.

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