uae_source_health

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

The description mentions 'live, timeout-bounded' but does not disclose whether the probe is read-only or has side effects, response behavior on success/failure, or any permissions needed. Since no annotations are provided, the description carries full burden and falls short.

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 sentence with no wasted words, but it could benefit from slightly more detail without becoming verbose.

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?

Given the tool's simplicity (one parameter, no annotations), the description still lacks key details like return value or behavior. An output schema exists but is not provided, so the description should compensate for that gap, which it does not.

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 sole parameter 'source_id' has no schema description (0% coverage). The description does not explain what the source ID represents, how to obtain it, or its format beyond the title 'Source Id'.

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 the action ('run') and the resource ('live, timeout-bounded health probe for one source'), distinguishing it from siblings like uae_source_get or uae_source_records. However, it does not elaborate on what the health probe entails, leaving some ambiguity.

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?

No guidance on when to use this tool versus alternatives like uae_source_get or uae_dashboard_summary. The description does not specify context, prerequisites, or when not to use it.

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