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

Annotations already declare read-only/open-world/non-destructive, so the description focuses on what they cannot express: the Cotlet API key requirement with app access, the ordering guarantee of returned answers, and the answers_limit=0 edge case. That is meaningful additive context for an auth-gated read.

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?

Front-loaded with the resource and return shape, then usage, then the edge case and auth note. Four sentences with minimal waste, though the second sentence partially restates the first.

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?

No output schema exists, and the description compensates by describing returned fields (text, answer count, top answers with author/upvotes) and their ordering. Auth requirement and the answers_limit edge case are covered; pagination beyond answers_limit is the only thin spot.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema by clarifying that answers_limit=0 returns the question only, which is a behavioral consequence not stated in the schema's "0 to 20. Default: 5." question_url remains schema-documented only.

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?

States a specific verb and resource (get a question) and enumerates the payload: question text, answer count, and top answers with author and upvotes, in Quora's display order. This is clearly distinguishable from quora_search_questions, which finds questions rather than retrieving one.

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?

"Use it before answering, so your agent sees what is already said" gives a concrete use context and a decision rule for calling it. It stops short of naming alternatives (e.g. search_questions for discovery, post_answer as the follow-up action), so it is clear but not fully routing.

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