list_nodes

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

No annotations are provided, so the description carries the full burden. It only mentions the return format but fails to disclose whether the operation is read-only, requires authentication, has pagination, or any side effects. This is insufficient for an agent to assess behavior.

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 very short and front-loaded, but it is under-specified. While concise, it sacrifices useful detail that should be present. It earns a passing score for brevity but lacks necessary substance.

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 simplicity of the tool (one optional parameter, no output schema), the description is incomplete. It omits the meaning of the filter parameter and any behavioral context (e.g., rate limits). An agent would need to guess or rely on external knowledge.

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 input schema has one parameter (filter_type) with 0% description coverage, and the description does not mention or explain it. The agent has no information about what filter_type does, its valid values, or how it affects results.

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 'List nodes' which is a clear verb+resource, distinguishing it from sibling tools like add_node or delete_node. However, it lacks specificity about what the list includes (all nodes? filtered?) and could be more precise given the context.

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 on when to use this tool versus alternatives like list_node_types or search tools. There are no explicit when-to-use or when-not-to-use instructions, leaving the agent to infer usage without help.

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