List Nodes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds a summary of filtering capabilities, but these are already fully documented in the schema. It does not disclose additional behavioral traits such as pagination defaults, ordering, or output format, so value beyond annotations is limited.

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 sentence of 12 words, front-loaded with the action and resource. It contains zero filler and every word contributes to the meaning.

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 8 optional parameters and no output schema, the description is minimal but adequate. It does not mention return structure, pagination behavior, or default limits, which are not covered by annotations. The schema handles parameters, but the description adds little to the overall contextual picture.

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 description coverage is 100% with detailed descriptions for all 8 parameters. The description mentions only a subset of filter fields (type, status, tags, git branch) and adds no new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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's function: 'List nodes with filtering by type, status, tags, and git branch.' The verb 'List' specifies the action, 'nodes' is the resource, and the filter dimensions differentiate it from sibling tools like get_node (singular) and add_node. It is concise and unambiguous.

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 implies usage (when you need to list/filter nodes), but it does not provide explicit when-to-use guidance or mention alternatives like search_nodes or get_subgraph. No exclusions are stated, so usage is only inferred from the name and description.

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