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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no indication of whether the run is polled, whether a run can be pending/in-flight, or what happens if the job is unknown.

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?

It is a single short fragment with no wasted words, but the brevity comes from under-specification rather than discipline. There is no structure or front-loading to speak of.

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?

An output schema exists, so return values need not be explained, but for a tool with a required undocumented parameter and jargon-heavy subject matter ("card button", "run") the description leaves the agent unable to invoke it confidently.

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 parameter "job" is an undescribed bare string. The description never explains what a job identifier is, where it comes from, or its expected format, so it fails to compensate for the schema gap.

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 fragment "the state of a card button's run" largely restates the title "Check card button" with the word "run" appended, and never supplies a verb. It hints at the resource but gives no grasp of what a "card button" or a "run" is, so it does not clearly separate itself from keeploop_card_action or keeploop_card_thread.

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 only guidance is the cryptic prefix "Card only", which is a scope constraint rather than a when-to-use rule. Nothing tells the agent when to call this versus keeploop_card_action, keeploop_card_thread, or keeploop_inbox, and no preconditions are stated.

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