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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implicitly indicates a read-only operation by describing a status report, but it does not explicitly state that it has no side effects or that it is safe to call. It does add context about what information is returned (integrations, token validity, quota), which is useful. A more explicit statement about being read-only would improve transparency.

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 two sentences with no filler. The primary purpose is front-loaded, followed by a clear usage directive. Every word earns its place, making it highly efficient and easy for an agent to parse.

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's simplicity (no parameters, no output schema), the description is quite complete. It states what information the agent can expect and when to call it. The only minor gap is that it doesn't describe the exact response format or structure, but the categories it lists are sufficient for most use cases. With no output schema to reference, a bit more detail on response fields would be ideal, but it's adequate for the tool's scope.

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 tool has zero parameters, so the schema is trivially complete. Per the rubric, the baseline is 4. The description adds value by explaining what the tool returns (integrations, token validity, quota usage), which goes beyond the empty schema. No further parameter explanation is needed.

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's purpose: reporting on deployment capabilities, token validity, and quota usage. It uses a specific verb ('report', 'tell you') and a specific resource (deployment status), and it distinguishes itself from the sibling tools by focusing on overall system status rather than a specific action. The phrasing 'What this deployment can actually do right now' is concrete and sets it apart from action-oriented siblings.

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 explicitly states when to call the tool: 'Call it when a tool refuses and you want to know whether the feature is off or used up.' This provides clear context and a specific trigger condition. However, it does not mention when not to use it or suggest alternative tools, so it stops short of the full 'when/when-not/alternatives' guidance that would earn a 5.

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