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

Goes well beyond the annotations by disclosing the required auth and scopes (accounts:read + posts:read), that the first answer never opens a human ticket, and the exact gated path to escalation. This resolves the ambiguity of readOnlyHint=false and destructiveHint=false by explaining precisely when a side effect can occur.

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?

Three dense but front-loaded sentences: purpose first, then auth/scopes, then the escalation contract. No filler, though the escalation sentence is long and packs several conditions into one clause-heavy run.

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 an 8-parameter, multi-turn tool with no output schema, the description covers the important non-obvious behavior (auth, two-step escalation gating). It omits any hint of what the first answer returns or how diagnostics surface, but that gap is minor given the absence of an output schema.

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 88%, so the baseline is 3, but the description adds cross-parameter semantics: that request_human and confirm_escalation only take effect together with a continued conversation (conversation_id) and a prior assistant answer. That relational meaning is not captured by the per-field schema descriptions.

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 ('Ask') and resource ('posterly Support AI'), plus the scope ('for the caller workspace') and the inputs it draws on (docs plus read-only account/post diagnostics). No sibling tool offers support-AI Q&A, so it is trivially distinguishable from list_conversations, manage_conversation, and submit_agent_feedback.

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?

Clearly explains the conditions that select ticket creation (continued conversation with a prior assistant answer, request_human=true, confirm_escalation=true, and explicit user confirmation). It stops short of naming alternative tools or stating when NOT to use this at all, so it is clear context without explicit alternatives.

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