keyso_get_clustering_node_uid_id_keywords

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention pagination, sorting behavior, filtering capabilities, response structure, or what 'keys' means. The example URL hints at query parameters but does not explain expected behavior or outcomes.

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 short but under-specified rather than concise. It consists of a vague phrase and a raw API path/example, lacking structure and front-loaded key information. It does not effectively communicate the tool's purpose or usage.

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 tool with 8 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the response contains, how filters work, or how to construct a valid request beyond the example. An agent would have to infer most behavior from the schema and example, which is insufficient.

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%, so the baseline is 3. The description does not add any semantic meaning beyond the schema; it only shows an example URL with sort and pagination parameters, which is not an explanation. The parameter descriptions in the schema are self-explanatory, so the description adds minimal value.

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 'clustering result, keys in the folder' which is vague and lacks a clear verb or resource description. It does not explicitly say it retrieves keywords for a specific node; the name implies it, but the text is ambiguous and could be interpreted as a label rather than an action. It does not distinguish this from sibling tools like keyso_get_clustering_node_uid.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, when it is appropriate, or which sibling tools to choose instead. The description provides only a path and example URL, with no usage context.

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