hcm_search_aor

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

The readOnlyHint annotation is true and the description's 'Search' is consistent with a read-only operation, so there is no contradiction. However, the description adds no behavioral context beyond the annotation, such as pagination behavior, result format, or that multiple results are returned.

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 concise and front-loaded with no filler. It is not a tautology, but it may be too terse to carry the operational detail an agent needs.

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?

For a search tool with no output schema and no parameter descriptions, the description is incomplete: an agent cannot determine what q accepts, how limit/offset work, or when to choose this over hcm_get_aor.

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%, and the description does not explain the q, limit, or offset parameters. The word 'Search' weakly implies q is a query term, but the description does not compensate for the schema's lack of semantic detail.

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 states a clear verb ('Search') and resource ('areas of responsibility'), aligning with the tool name. It is not a tautology and is broadly distinguishable from the sibling hcm_get_aor, though it does not define the search scope or result shape.

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?

There is no guidance on when to use this tool versus alternatives like hcm_get_aor or other search tools. No mention of filters, prerequisites, or exclusions; the only usage signal is the implicit convention that 'search' means query-based lookup.

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