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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, whether it reaches the network or parses local logs, what it returns for a bad errorText, or any limits. A single parenthetical '(diagnostic)' conveys no behavioral trait at all.

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 short, but the brevity comes from under-specification rather than efficiency — the one line is a name echo with a category label and no useful content. There is nothing to front-load because nothing informative was written.

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 annotations and no output schema, the description is the only place an agent could learn what this diagnostic produces (findings, severity, remediation pointers), and it supplies none of that. For a diagnostic tool taking a free-form error excerpt, this is completely inadequate.

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 100%: the single parameter errorText is documented in-schema as a 'Sanitized error or log excerpt' with an 8000-char cap. Per the baseline for high coverage, the description need not add parameter detail, and it indeed adds none.

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 is essentially a restatement of the tool name and namespace ('MediaSFU Flutter :: runtime.diagnose') plus the bare category tag '(diagnostic)'. It does not state what the diagnostic actually inspects or returns, so an agent cannot distinguish it from siblings like fix.suggest or env.preflight beyond the word 'diagnose'.

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 when-to-use guidance, no prerequisites, and no named alternative among the ~13 sibling tools per platform. The only usage signal is implicit in the name 'diagnose', which is not enough to route an agent between runtime.diagnose and runtime.readiness.diagnose or fix.suggest.

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