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

Annotations provide readOnlyHint=true, and the description reinforces this as a 'diagnostic' call. The description adds valuable transparency about what data is returned (enumerates all 7 fields) and the logical interpretation of that data (mismatch semantics). While it doesn't discuss rate limits or auth, the description meaningfully extends beyond the annotation for a benign zero-arg call.

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?

Two sentences, well-structured and front-loaded with the core purpose before giving a practical use case. The second sentence is a bit long and runs into a single lengthy clause, but it earns its place by conveying a real-world diagnostic workflow. Slightly verbose relative to the simplest possible version, but not padded.

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 an output schema available, the return-value enumeration is somewhat redundant with structured data, but the tool description still adds a complete diagnostic narrative. The tool is simple (zero args, benign), so the description is arguably complete. Minor gap: doesn't mention that this is the safe/cheap way to introspect the environment beyond schema staleness.

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?

Zero parameters, so schema coverage is 100% with nothing to document. The description does not need to add parameter meaning since there are no parameters; however, it compensates by explaining the semantic meaning of the returned fields (schema_hash comparison workflow), which functions as the equivalent value-add here.

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?

Clear verb+resource: 'Zero-argument diagnostic call' returning exactly the listed fields (build_sha, schema_version, etc.). The purpose is specific and unambiguous, and it distinguishes itself from sibling tools by being the one diagnostic/version-status function among a large set of domain tools.

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?

Explicitly states when to call it ('confirm you're seeing the current deployed schema', 'if a tool you expect like house_specify seems to be missing, call this first'), provides a concrete workflow (compare schema_hash against another connection), and explains the diagnostic interpretation (mismatch = stale cached manifest, not deployment gap).

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