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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the action without revealing any behavioral traits such as rate limits, authentication needs, pagination, or result handling. It does not contradict annotations, but it is far from transparent about how the tool behaves.

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, focused sentence with no extraneous words. It front-loads the core purpose and is appropriately sized for a simple tool. While it could add more detail, it does not waste space.

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 tool's simplicity (one optional parameter) and the existence of an output schema, the description provides the core purpose but lacks any context about when to use it, what it returns (though output schema covers that), or any constraints. With over a hundred sibling tools, the lack of differentiation and usage context makes it incomplete for an agent to correctly select and invoke it.

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?

The schema has zero description coverage, so the description must compensate for the parameter 'q'. The description implies that 'q' is the display name to search for, which adds meaning beyond the bare schema. However, it does not clarify whether 'q' is a partial or exact match, whether it is required, or any format expectations. It provides partial semantic guidance.

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 specific verb ('search') and a clear resource ('SO/SE user') with a scoping qualifier ('by display name'). It distinguishes the tool from generic Stack Overflow tools, though it does not explicitly differentiate it from sibling 'sopostuser', which might perform a similar function. The purpose is unambiguous and not a tautology.

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. There is no mention of scenarios where this should be preferred, no exclusions, and no reference to sibling tools. Given the large sibling list, an agent would have no basis to select this over similar search tools.

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