explain_concept

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

With no annotations, the description carries the full burden. It does disclose one genuine behavioral trait — that it consumes no MCP calls (i.e. no cost/rate-limit concern) — which is valuable. But it says nothing about output format, permissions, or whether it is read-only, leaving a modest gap.

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 with the verb and topic stated first and the cost note second. No wasted words, though it is terse enough that it stops short of explaining the return.

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?

For a simple 1-param, 0-required tool with no output schema, the description covers purpose and cost but omits any indication of what the explanation looks like or how detailed it is. Adequate but leaves a gap the missing output schema does not fill.

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 0% and there is one enum parameter (topic: neat|met). The description names both 'NEAT' and 'MET', implicitly mapping to the enum values, so it partially compensates. It adds no further meaning about acceptable values or defaults.

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 (科普/explain) and resource (NEAT / MET 的含义与依据), so the agent knows this is an informational/reference tool rather than a computation. It is clearly distinguishable from siblings like walk_allowance and what_can_i_eat, 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 '不消耗任何 MCP 调用' implies you can call this freely when you need background on NEAT/MET, which is a usable context hint. However, there is no explicit when-to-use/when-not statement and no reference to alternative tools for related questions.

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