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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description adds real value by disclosing the return shape (phase, PIs, counts, citable amira_url) and a data caveat that AM 2.0 sections are newly seeded and currently hold ~0 projects/items, which prevents the agent misreading empty results as an error.

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?

Front-loaded with the core purpose and invocation constraint, then adds detail. The enumeration of all twelve section names is lengthy but does help the agent recognize the expected output; it is the one passage that could be trimmed without losing invocation-relevant meaning.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so concretely (funding phase, PIs, member/project/item counts, amira_url). Combined with the seeding caveat and the sibling pointer, an agent has everything needed to call and interpret this tool.

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?

Zero parameters, so the baseline is 4. The description confirms 'Takes no arguments,' which matches the empty schema and additionalProperties:false, leaving no ambiguity about how to invoke it.

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 ('the cluster's research sections'), and immediately qualifies the scope as 'top-level thematic structure' with the return fields (funding phase, PIs, counts, amira_url). It is clearly distinguishable from get_research_section, which returns a single section's detail.

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?

Explicitly routes the agent: use get_research_section 'for one section's full description and project list.' This gives a clear alternative and the condition that selects it, though it doesn't spell out a when-not for this tool beyond that single contrast.

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