cnki_structured_search

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

Annotations already declare readOnlyHint and openWorldHint. The description adds the behavioral trait of strict execution of caller-specified conditions, which is useful context. However, it does not disclose session requirements, pagination behavior, or rate limits, which are relevant for a retrieval tool.

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 a single sentence with no redundant wording, front-loading the core purpose and key behavioral trait. It is highly concise and efficient, earning a perfect score on this dimension.

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?

The tool is complex with 11 parameters and likely depends on a CNKI session (sibling cnki_login exists). The description does not mention prerequisites, typical use cases, or how it differs from cnki_search in practical terms. Even with an output schema, the description leaves significant gaps in operational context.

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 64%, so the schema already documents many parameters. The description adds emphasis on fields, Boolean relations, and match modes, which clarifies the conditions array semantics. But it provides no added meaning for other parameters like limit, pages, or metadata_depth.

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 identifies it as a structured CNKI search tool with a specific focus on fields, Boolean relations, and match modes. This distinguishes it from the generic cnki_search sibling, though it does not explicitly name the alternative.

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 precise, structured queries via '严格执行调用者指定的...' but provides no explicit when-to-use or when-not-to-use guidance compared to cnki_search. There are no stated exclusions or alternatives, so the guidance is implied rather than explicit.

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