pack_neighborhood

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

With no annotations, the description should disclose behavioral traits. It mentions 'source packed in topological order to a token budget' but does not clarify side effects, output format, or required permissions. The behavior is opaque.

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, making it concise. However, it is cryptic and lacks structure, reducing readability and clarity. It would benefit from clearer organization.

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?

No output schema is provided, and the description does not mention what the tool returns. For a complex operation like packing a neighborhood, this is a critical gap. The tool's role among siblings (e.g., locating, searching) is also unclear.

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 0%, so the description must compensate. It relates 'hops' to 'k-hop dependency' and 'budget' to 'token budget', but does not explain each parameter's meaning, format, or constraints. The description is insufficient for understanding parameters.

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 mentions 'k-hop dependency neighborhood' and 'packed in topological order to a token budget', which gives a vague sense of the operation. However, it lacks a clear verb and does not explicitly state what the tool returns or accomplishes, making it moderately unclear.

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 is provided on when to use this tool versus alternatives. The phrase 'single-shot static fallback' hints at a fallback role but does not specify context or conditions.

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