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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that sources are 'verified', with no note on pagination, rate limits, or ordering. With annotations carrying the behavioral load, a 3 is appropriate.

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 tight sentences, purpose front-loaded before the usage directive. 'With supported operations and filters' is the only vague filler and slightly muddies the first sentence.

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?

An output schema exists, so return values need no explanation, and the tool is a parameterless read-only catalog. The description covers purpose and workflow placement; it is adequate for such a simple tool, though it could say more about what distinguishes a usable source.

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 the baseline is 4. The schema is trivially complete (additionalProperties false, no fields), and the description's mention of 'supported operations and filters' plausibly refers to fields inside the returned source records rather than inputs.

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 clear verb (List) and resource (verified scholarly source records), and the phrase 'catalog to select sources' distinguishes it from research_search_papers. The clause 'with supported operations and filters' is slightly ambiguous about whether it describes the returned records or operations on them, but the core purpose is legible.

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?

'Use this catalog to select sources before searching papers' gives a clear workflow position and implicitly points at research_search_papers as the downstream alternative. No explicit when-not condition or named sibling, but the usage context is clear.

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