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

With no annotations, the description carries the burden of behavioral disclosure. It enumerates the return fields but does not explicitly state that the operation is read-only or has no side effects. The name 'status' and the nature of the fields strongly imply a safe read, but this is not stated. It also does not mention any authentication or error conditions.

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 a single, dense sentence that front-loads the primary content (counters, quotas) and then details the index block. It is efficient and avoids fluff, though it could be slightly better structured with a leading verb.

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?

The description lists all returned fields explicitly, which is essential since there is no output schema. Field names are self-explanatory. It does not cover error handling or prerequisites, but for a status read these are less critical. Overall, it provides enough context for an agent to understand what the tool returns.

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 single optional parameter tenant_key is fully documented in the schema (100% coverage), including when it is required. The description does not add any parameter-specific guidance, but the schema already covers it, so the baseline of 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?

The description clearly states the tool returns document store counters, quotas, and index status fields. The verb is implicit ('status' implies retrieval), but the content is specific and distinct from siblings like host.docs.list or host.docs.get, which operate on individual documents.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that it's a read-only status check, nor does it contrast with host.docs.index_config or host.docs.list. An agent must infer from the name that it's a status endpoint.

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