cat_nodeattrs

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

No annotations are provided, so the description carries full burden. '获取节点属性' implies a read-only operation, but doesn't disclose any behavioral traits like authentication requirements, rate limits, output format, or whether it's a real-time vs cached view. For a tool with zero annotation coverage, this is insufficient.

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 extremely concise (4 Chinese characters), but this brevity comes at the cost of being under-specified rather than efficiently informative. While front-loaded, it lacks the necessary detail to be truly helpful.

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?

Given the complexity of Elasticsearch operations and the lack of both annotations and output schema, the description is incomplete. It doesn't explain what 'node attributes' includes, the return format, or how this differs from other node-related tools. For a tool in a rich ecosystem with many alternatives, more context is needed.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and the baseline for 0 parameters is 4. No additional parameter semantics are required.

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 '获取节点属性' (Get node attributes) restates the tool name 'cat_nodeattrs' (catalog node attributes) almost verbatim, making it tautological. While it indicates a read operation on node attributes, it doesn't specify what kind of attributes or how this differs from sibling tools like 'cat_nodes' or 'nodes_info'.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools related to nodes (cat_nodes, nodes_info, nodes_stats, nodes_usage, nodes_hot_threads), the description offers no context about when this specific node attributes catalog tool is appropriate.

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