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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful context beyond these flags: it specifies which data sources are tracked for lag, reports UTC reset time for quota, and notes which tools the key can call. This gives a fuller behavioral picture without contradicting the annotations.

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 a single, information-dense sentence with no filler. It front-loads the tool's purpose and then enumerates the meaningful status components; every detail from source categories to lag units, coverage, key access, and quota reset timezone earns its place.

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 zero parameters and an output schema present, the description covers everything an agent needs: freshness per source, tracking coverage, accessible tools, quota usage, remaining quota, and reset time. No critical information is missing for deciding to call and interpreting this status tool.

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 is empty and there are no parameters, so the parameter-semantics burden is minimal. The description confirms the tool takes no inputs by focusing entirely on what the status response contains, which is appropriate for a zero-parameter tool.

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 defines jt_status as a health/status endpoint for the Jet Tracker data layer, listing exact reports such as last sync per source, lag in hours, tracking coverage, key access, and daily quota. This differentiates it from the many sibling lookup/fleet/search tools by focusing on data freshness and quota rather than a specific data query.

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?

Usage is implied rather than explicit: the phrase 'Health of the Jet Tracker data behind the tools' and the quota fields signal that an agent should call this to verify data freshness or available quota before relying on other jt_* tools. However, there is no explicit when-to-use or when-not-to-use statement, and no alternative tools are named.

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