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

No annotations are provided, so the description carries the full burden. It does disclose useful non-obvious behavior: credentials come from the caller's OpenAny gateway, charges/authorization are gateway-determined, and question bodies are truncated to 300 characters. It does not state that the operation is read-only, nor does it describe rate limits, failure modes, or result ordering beyond what `sort` implies.

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?

Two sentences, front-loaded with the resource and scope, and the second sentence covers credentials/cost. The returned-field enumeration is long but earns its place since no output schema exists. Slight redundancy with the nested schema text, which repeats the same sentences.

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?

With a single nested parameter and no output schema, the description supplies the return-field inventory and the 300-character truncation, which is exactly what the agent needs to judge usefulness. Missing pieces are minor: no pagination note beyond `limit`, and no statement of a read-only safety profile despite the absence of annotations.

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%, and the schema already documents the `sort` enum and `limit` maximum/default, so the description largely restates structured data. It does add the semantic that `tag` scopes results to questions carrying that tag, but `tag`'s own schema description is empty and no tag syntax (multiple tags, hyphens) is explained.

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 opens with a specific verb and resource ('Questions on Stack Overflow with a tag') and names the upstream source (Stack Exchange API), so an agent knows exactly what is being retrieved. It does not explicitly distinguish itself from sibling crawl4ai endpoints (Medium posts, RemoteOK jobs, research papers), but the tag-based Stack Overflow scope is unambiguous.

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 choose this tool versus alternatives; no mention of when-not-to-use, no pointer to sibling search tools. The only usage constraint ('Tag-based question discovery, not full answers') appears in the nested schema description rather than the tool description, so the top-level text leaves routing entirely to inference.

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