cnki_get_citations

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

No annotations are provided, and the description does not disclose any behavioral details such as read-only nature, potential rate limits, authentication requirements, or side effects. Without this information, an agent cannot anticipate operational constraints or error conditions.

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?

The description is concise, consisting of two sentences that efficiently state the purpose, input, output, and optional parameter. No unnecessary information is included, and the structure is clear and direct.

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?

Given the absence of an output schema and annotations, the description provides sufficient context for basic use: it explains what the tool does and what inputs are needed. It does not describe the return format, but this is not strictly required for invoking the tool. Minor omission is the lack of detail on how the returned citation data is structured, but this is not critical for selection.

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?

Both parameters are thoroughly explained. The description defines 'url' as the article detail page URL and 'tabs' as the citation types, listing all possible values and the default. This adds meaning beyond the schema, which only repeats the same descriptions, by clarifying the default behavior.

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 retrieves citation network information for CNKI papers, specifically references and cited literature lists. It uses the verb '获取' (get) and specifies the resource (article detail page URL), making the purpose unambiguous and distinct from sibling tools that handle searches or article details.

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 usage for citation data retrieval, and the input URL and optional tabs parameter provide clear guidance. It does not explicitly contrast with sibling tools like cnki_get_article, but the specialized focus on citations makes appropriate usage inferable. Lacks an explicit 'when not to use' statement.

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