Verify OneHome auth + GraphQL reachability

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

Description explains query selection logic, return values (auth mode, token expiry, elapsed time, error detail), and that it's a round-trip. Annotations already indicate readOnly, idempotent, openWorld; description adds concrete behavioral context without contradiction.

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?

Three concise sentences covering action, session-specific behavior, return values, and usage recommendation. No unnecessary words.

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?

Fully describes the healthcheck behavior, return fields, and purpose. No output schema needed given the description covers key outputs.

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?

No parameters exist in schema; description doesn't need to add parameter info. Baseline 4 for zero-parameter tools.

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?

Clearly states the tool performs a round-trip authenticated query to verify auth and GraphQL reachability, with specific query selection based on session type. Distinguishes itself from sibling data-retrieval 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 advises to run this first when a tool fails to isolate auth issues from API misbehavior, providing clear when-to-use guidance.

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