np_squeeze

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

With no annotations present, the description carries the full burden of disclosing behavioral traits. It fails to mention that the operation returns a new array (rather than modifying in place), what happens if no singleton dimensions exist, or how axis selection behaves in detail. The brief description leaves significant behavioral gaps.

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 that directly states the purpose. It is efficient and front-loaded with no unnecessary words.

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 presence of an output schema (presumably documenting the return type), the description is partially complete. However, it omits important context such as whether the output is a view or copy, and what happens for degenerate inputs (e.g., empty array or array with no singleton dimensions). The tool's simplicity means a score of 3 is adequate but not fully comprehensive.

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% (both parameters have descriptions in the schema), so the baseline is 3. The description itself does not add any additional semantic detail beyond what is already in the schema, such as clarifying that 'axis' can be an integer or array of integers.

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 uses a clear verb ('Remove') and specifies the resource ('single-dimensional entries from the shape of an array'), which precisely identifies the operation. It distinguishes from sibling tools like np_reshape (general reshaping) and np_flatten (to 1D) by focusing on removing axes of length 1.

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 like np_reshape or np_flatten. The description only states what it does, without any context on when it is appropriate or inappropriate, leaving the agent without decision support.

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