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

With no annotations provided, the description carries the full burden. It discloses that the tool returns actual live state ('the truth', 'not a generic warning'), details what it checks, and notes that it routes through the Builder rather than a direct Core call. This adds significant behavioral context beyond a simple 'verify' label, though it doesn't explicitly discuss side effects, permissions, or output 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 concise and well-structured. It opens with a compelling 'ONE call' hook, then explains what it returns, when to use it, and why it's reliable. Every sentence adds value without redundancy.

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 (one parameter, no output schema), the description is remarkably complete. It covers the tool's capability, usage timing, and technical routing, giving an agent everything needed to decide when and how to invoke it.

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 fully covers the single parameter (solution_id) with a clear description and 100% coverage. The tool description does not add additional parameter semantics, but the schema is sufficient, so the baseline of 3 is appropriate.

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 specifies a clear verb ('returns') and resource ('REAL runtime end-state of a solution'), enumerating concrete checks (connectors connected, tools discovered, widgets rendering, skills deployed) and explicitly claims it identifies 'the EXACT failing gaps'. This distinguishes it from generic verification tools and sibling tools like ateam_status_all or ateam_verify_consistency.

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 an explicit usage context: 'Use this instead of guess-and-check after a deploy/patch'. This is a clear when-to-use directive. However, it does not name specific alternative tools or state when not to use it, so it falls short of a full 5.

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