list_concepts

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that it lists all concepts and does not mention return format, ordering, pagination, scope limits, or whether any side effects are possible. It is not misleading, but it is very thin.

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 clear sentence with no filler or redundancy, and the core action is front-loaded. It is appropriately concise for a simple tool, though it is sparse enough that it cannot earn a 5.

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 no output schema and no annotations, the description should explain what the agent can expect from the call. It does not describe the return value, whether results are complete in one response, or how this tool differs from related list/read tools. For a simple no-parameter tool it is close to adequate, but the missing return and distinction details leave notable gaps.

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?

The tool has zero parameters and an empty schema, so parameter semantics are trivially complete. The description adds nothing about parameters, but none exist; this matches the baseline 4 for a no-parameter tool.

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 states a specific verb ('列出'/'list') and a resource ('concept'), and '所有'/'all' clarifies the scope as a full listing. It is distinguishable from siblings like read_concept or list_entities by the combination of verb and resource, though it does not explicitly name or contrast them.

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 provides no guidance on when to use this tool versus alternatives such as read_concept for a single concept or list_entities for entities. The intended usage is only implied by the verb and resource, with no exclusions or alternative routing.

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