searchNodes

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

Annotations are absent, so the description carries full burden for behavioral disclosure. It only states 'search nodes by criteria' without revealing whether the operation is read-only, how results are returned, pagination behavior, or filtering semantics. This leaves critical behavioral aspects unaddressed.

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, front-loaded sentence that efficiently states the core purpose. It is concise, but the brevity sacrifices substance—key context about usage and behavior is omitted, making it somewhat under-specified rather than appropriately concise.

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 there are 6 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, result format, or any behavioral constraints. The agent would need to look elsewhere for essential context, making this insufficient for a tool of this complexity.

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%, so all parameters have individual descriptions. The tool description adds no additional meaning beyond what is already in the schema, which is acceptable given the high coverage. 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 'Search nodes by criteria' clearly identifies a search operation on nodes with criteria-based filtering. It uses a specific verb and resource, but 'criteria' is vague and it does not differentiate from the sibling tool queryNode, which likely serves a similar purpose.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives like queryNode or listProjects, nor does it mention any prerequisites or exclusions. The agent is left to infer the intended use case.

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