Check tenant status

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

With no annotations, the description carries the full burden. It discloses the conditional return of an embed snippet and steps at the live stage, which is helpful. However, it does not explicitly state whether the operation is read-only or if there are side effects, errors, or authentication requirements.

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 concise, consisting of three short sentences with no redundant content. It efficiently conveys the core functionality, polling behavior, and conditional output.

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 there is no output schema, the description sufficiently enumerates the returned fields (lifecycle stage, worker phase, pages crawled, domain verification) and the conditional embed snippet and steps. It also provides usage context, making the tool easy to invoke correctly.

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 only parameter, tenant_id, has a clear description: 'tenant id returned by answerhatch_create_tenant'. This directly tells the agent where to obtain the value, fully clarifying its semantics.

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 that the tool reports a tenant's lifecycle stage, worker phase, pages crawled, and domain verification. The title 'Check tenant status' reinforces the purpose, and it is distinct from the sibling tools (login, create_tenant, start_crawl).

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?

Explicit guidance is given: 'Poll this every 20 to 30 seconds while a crawl runs.' It also explains the conditional behavior when the stage reaches live, providing clear when-to-use and what-to-expect instructions.

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