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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds genuinely useful behavior beyond that: questions in Spaces where the user is not a contributor require admin/moderator approval, the call is confirming-by-default but can be toggled, and it reaches other people so user confirmation is needed. This is solid added context, though permissions/keys are only vaguely described.

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-loads the core action, but the confirmation theme is stated twice ('By default you confirm each call' and 'confirm with the user before each call'), which is redundant. The Cotlet API key sentence is tacked on at the end without much structure.

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 two-parameter mutation tool with no output schema, the description covers the key things an agent needs: approval semantics, confirmation policy, external reach, and an auth prerequisite. Nothing critical is missing, though per-Space permission details remain thin.

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 both the required 'question' (with its trailing-question-mark constraint) and the 'space_id' targeting parameter are already fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 ('Add a new public question to Quora') and clarifies it posts under the user's name. It is distinguishable from sibling quora_post_answer, though it does not explicitly contrast with quora_post_to_space even though a Space-targeting parameter exists here.

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?

Gives useful context about the approval flow and the confirm-before-each-call requirement, which implies when this is appropriate. However, it never names alternatives like quora_post_to_space or quora_search_questions, so the agent gets implied rather than explicit routing guidance.

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