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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful context beyond annotations, including quota reset timing, key-scoped tool access, and the reconnect action on toolset hash mismatch.

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 front-loaded with the core purpose and then enumerates the returned status items efficiently. It is dense but appropriately sized for a status tool covering several sources and quota details.

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?

With no parameters, rich annotations, and an output schema present, the description provides enough context for correct invocation. It explains what status domains are covered and gives the one operational instruction needed when version state is stale.

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 takes zero parameters, which is the baseline 4 case. There are no input semantics that need explanation.

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 that this tool reports the health of the Jet Tracker data behind the tools, and it enumerates the specific status items returned: server version, toolset hash, source sync freshness, coverage, callable tools, and quota. This distinguishes it from all sibling tools, which are data query or watch 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?

The description gives clear context for using it as a health/quota check and includes one explicit conditional action: reconnect the connector if the toolset hash differs from what the client loaded. It does not explicitly say when not to use it or compare it to alternatives, but no sibling status tool exists.

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