search_units

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

The description discloses no behavioral traits beyond the annotations. It does not mention pagination, required body parameters, or the nature of the operation (read vs. write). While annotations indicate readOnlyHint=false, the description adds no context about safety or side effects.

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 extremely brief, but this is under-specification rather than conciseness. It does not provide any structured information or front-loaded value; it merely repeats the tool name in a readable format.

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?

The tool has a required 'body' parameter that is an array of objects, but the description gives no hint of what the body should contain or how the search works. With no output schema and limited annotations, the description is wholly inadequate for an agent to understand how to invoke the tool correctly.

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 the schema already documents all three parameters (body, limit, offset). The description 'Search units' adds no meaning beyond the schema, which is a baseline of 3.

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 units' is an exact restatement of the tool name and annotation title, adding no additional specificity or scope. It fails to distinguish this tool from sibling tools like list_units or get_unit, both of which also relate to retrieving units.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of search criteria, filtering, or how it differs from listing all units (list_units) or fetching a single unit (get_unit).

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