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

The annotations (readOnlyHint=true, destructiveHint=false) are consistent with a status read operation. The description adds valuable behavioral context: it requires business permissions, has a restriction on free accounts, and mandates a prerequisite call to check_business_tool_access. This goes beyond what annotations alone provide, though it does not detail the exact status values or response format.

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 description is four sentences long, front-loaded with the purpose. It covers key usage notes without unnecessary verbosity. The structure could be slightly improved by separating parameter explanations, but it is currently efficient and to the point.

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?

Given the tool is a simple status getter with two required parameters and no output schema, the description adequately covers permissions and preconditions. However, it omits explanations of the parameters and what the returned status looks like. This leaves the agent with gaps in understanding the full context of the tool's usage and output.

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?

The input schema lists two required parameters (communityId, orderObjectId) but has 0% description coverage. The tool description does not explain what these parameters represent, their format, or how they are used. For example, it does not clarify that communityId identifies the managed community or that orderObjectId is likely the order identifier. With no schema descriptions, the description should compensate but fails to do so.

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 clearly states the action: 'Get custom-domain order status for a managed community.' It specifies a verb (Get), a specific resource (order status), and the target scope (managed community). This differentiates it from sibling tools like get_custom_domain_status or get_community_custom_domain_status, which address different aspects of custom domains.

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?

The description provides explicit preconditions: check business permissions, note that FREE businesses cannot use this tool, call check_business_tool_access first, and handle grace-period warnings. It gives clear when-to-use guidance and what not to proceed with when blocked. However, it does not explicitly distinguish from other status-related sibling tools, which would elevate it to a 5.

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