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

The description frames the tool as a pure read operation (search and return metadata/excerpts), yet the annotations declare readOnlyHint=false, which asserts the call is not read-only. This is an outright contradiction between the prose and the structured hints, which per the rubric caps this dimension at 1 despite the useful note about bounded metadata and body-text excerpts.

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?

A compact two-clause sentence that front-loads the verb and resource before the return-behavior detail. No filler, though the return-behavior clause is partly redundant given an output schema exists.

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 an output schema present, return values need not be explained, and the schema documents most parameters, so the core calling contract is covered. However, the missing usage guidance and the unresolved readOnly contradiction leave meaningful gaps for a 5-parameter, multi-source search 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?

Schema description coverage is 80% (query, date_from, date_to, sources all documented; only 'limit' bare), so the schema already carries the parameter burden and baseline 3 applies. The description adds no parameter-level meaning, syntax or defaults beyond what the schema provides.

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+resource ('检索研报和论文' – search research reports and papers), which is enough to distinguish it from content-type siblings like search_filings, search_meetings and search_visuals without opening their schemas. It does not explicitly name those siblings, so it stops short of a 5.

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 implies the tool is for research reports and papers but gives no explicit when-to-use vs when-not guidance and never names an alternative tool or the condition that would select get_evidence or search_filings instead. Usage is left entirely to inference from the resource noun.

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