查询 IsingQ 与伊辛智能公开知识

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by specifying the data source is a local, versioned knowledge pack requiring no API key, which is the one behavioral fact annotations do not convey (implication of possibly stale packaged data).

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 single front-loaded sentence that leads with the source and scope, then the offline/no-key constraint. The middle enumeration is long but each entry corresponds to a real query topic, so little is wasted; the semicolon split gives it a clean structure.

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-format explanation is unnecessary. For a simple two-parameter, read-only, idempotent lookup the description covers source, scope and auth requirements; only the locale parameter's role is left unaddressed.

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 coverage is 50%: topic carries a description and enum, locale has an enum but no description. The description's Chinese enumeration (光电伊辛机, 玉盘·伊辛云, 术语) usefully maps colloquial topics to enum values like ising_machine and glossary, but says nothing about locale or the zh-CN-only restriction, so it only partially compensates.

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?

Names a specific verb (查询) and a concrete resource (本机版本化知识包) and enumerates the covered domains (company, products, IsingQ, optical Ising machine, cloud, solutions, cases, FAQ, glossary), which maps cleanly onto the topic enum. It clearly is not a solve/modeling tool like its siblings, though it never names them explicitly.

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 clause '不联网，不需要 API Key' implies the operating context (offline, credential-free lookup) and therefore when this tool is usable, but it states no when-to-use condition, no exclusions, and no routing to the modeling/solve siblings. Usage is inferred rather than guided.

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