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

Beyond the readOnly/idempotent annotations, the description explains the meaning of skeleton=true ('authored half is empty'), the caveat that file=true is not coverage, and the absence of arguments. This adds useful behavioral context that an agent cannot infer from annotations alone.

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?

Three concise sentences front-load the core purpose, then clarify an important edge case (skeleton/file), and end with a practical pointer to get_company_file. No redundant words or repetition of structured data.

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-parameter listing tool with rich annotations and an output schema, the description covers the key field semantics, the most likely confusion (file=true), and the natural next step for reading a file. Nothing essential is missing.

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?

There are no parameters and the schema coverage is 100%, so the schema is complete. The description confirms 'No arguments' explicitly, which is the only necessary parameter-level guidance.

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 clearly states the tool lists the research hub's coverage universe: clusters and symbols with company-file revision, as_of date, compiled-file existence, and skeleton flag. It also clarifies 'file=true is not coverage', preventing a common misinterpretation, and ties to the sibling get_company_file for file contents.

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?

The description indicates the tool takes no arguments and points to get_company_file(symbol) as the alternative for reading a file. It does not explicitly compare against other siblings like read_research or search_research, but the context for when to use this listing tool is clear enough.

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