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

Annotations only cover the safety profile (readOnly, non-destructive, closed-world), and with no output schema the description carries the full return-value burden — it explains found, truncated, help_center_url, the loosely_related exclusion from found, and the precedence rule that platform_policy beats published articles. That precedence rule is genuinely non-obvious behavioral context an agent could not infer.

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 purpose is front-loaded, but the rest is a run-on paragraph that repeats the same idea twice ('it can still hold the answer, so read it' and 'can still hold the answer in other words') and mixes field definitions with precedence rules. It is understandable but does not justify its length.

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 no output schema, the description does the essential work of defining every response field and the platform_policy-vs-article conflict rule, which is what an agent needs to consume the result correctly. The gap is routing: nothing tells the agent when to escalate to support_create_ticket instead.

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?

There is one parameter with 0% schema description coverage, so the description must compensate; it implies the input is a natural-language question about platform behavior. It does not mention the 3–300 character bounds or anything about phrasing, so it only partially fills the gap.

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 opening sentence gives a specific verb and resource: answer a question about how Commonplace works, which is unambiguously the help-center search tool and distinct from support_create_ticket. It stops short of naming siblings or stating the scope boundaries that would make it a 5.

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?

Usage is implied by 'Answer a question about how Commonplace works,' and there is useful guidance on reading loosely_related and trusting platform_policy over articles. There is no explicit when-to-use-this-vs-alternative guidance, and support_create_ticket is never mentioned despite being the obvious sibling for unresolved questions.

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