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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the read semantics implied by 'Fetch' — no error behavior for unknown ids, no permission/ownership scope beyond the vague 'your', and no sense of what a check contains. 'Your checks' hints at user scoping but that is the only behavioral signal.

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?

A single front-loaded sentence with no filler, appropriately sized for a simple lookup. It is efficient, though brevity here edges into under-specification rather than deliberate conciseness.

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?

For a one-parameter read with no output schema, the definition is minimally sufficient to attempt a call. It still omits the id format and what the returned check looks like, which matters given the absence of structured documentation elsewhere.

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?

Schema description coverage is 0% and the single required check_id has no documented format. 'By id' is the only hint and it adds nothing beyond the property name, so the description fails to compensate for the coverage gap (e.g., id format, prefixes, whether it accepts names).

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 gives a specific verb (Fetch) and resource (a check) with the lookup key (by id), so the operation is unambiguous. It does not, however, differentiate this from siblings like check_card or list_watches, leaving the agent to infer which retrieval tool applies.

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?

There is no statement of when to use this versus list_watches (listing) or check_card (likely a card/detail view), and no prerequisites or exclusions. The agent must guess the routing from the tool name alone.

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