Fetch CNBS Nodes

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral detail about isEnd=true indicating setIds, which is useful beyond annotations. No contradictions with annotations.

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 with a clear Args section and Returns line. It is front-loaded with the purpose and every sentence provides value. No wasted words.

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?

Input schema is simple with no output schema, so the description must explain return values. It states the return is a list of tree nodes, grouped by category for multiple categories, but lacks details on node fields (e.g., id, name, isEnd). This is adequate but not fully complete.

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 100%, but the description adds significant domain-specific meaning: it explains the numeric code mapping for categories (e.g., '3' for 年度) and clarifies that parentId is only effective for single categories, going beyond the schema descriptions.

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 fetches CNBS classification tree nodes, with specific verb 'fetch' and resource 'nodes'. It distinguishes itself from siblings like cnbs_fetch_end_nodes by supporting multiple categories and explaining that nodes with isEnd=true are setIds.

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 mentions support for multiple categories and that parentId is only effective for a single category, but does not explicitly contrast with siblings like cnbs_fetch_end_nodes or provide when-to-use vs alternatives. Usage context is implied but not clearly bounded.

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