getNodesSummary

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

The description indicates a read operation (no destructive hints) and mentions grouping and statistics, which aligns with the schema. However, it lacks details on what statistics are included or the exact behavior of grouping, and no annotations are provided to supplement.

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, efficient sentence that communicates the core functionality and rationale without any redundancy or superfluous details.

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?

While the description covers the basic purpose, it does not elaborate on the structure of the summary output, the meaning of 'statistics', or how grouping affects the result. Given 4 parameters and no output schema, more detail would improve completeness.

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?

All 4 parameters have descriptions in the schema (100% coverage), so the description adds minimal value beyond reinforcing the concepts of grouping and statistics. The default values and enums are already clear from the schema.

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 identifies the tool's purpose: retrieving a summary of nodes with statistics and grouping. It distinguishes itself from sibling tools like getNodeInfo and findNodesByName by emphasizing token reduction and aggregated data.

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 a compact summary is needed ('to reduce token usage'), but does not explicitly state when to use this tool versus alternatives or provide exclusions.

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