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

With no annotations provided, the description carries the full behavioral burden, and it discloses little beyond the word 'Test'. It does not confirm the operation is read-only/side-effect free, does not say whether it persists anything, and does not describe what the parse result contains.

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 waste; the parenthetical earns its place by explaining the why. It is efficient, though the extreme brevity is part of the overall specification gap rather than a virtue in itself.

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?

No output schema, no annotations, and 0% parameter documentation mean the description must carry everything, and it does not. An agent cannot tell what the parser returns, how text vs html are prioritized, or whether this is safe to call repeatedly.

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% across four parameters (from_addr, text required; subject, html optional). The description says only 'email', which weakly implies the fields map to email components, but adds no format, required-ness, or precedence guidance to compensate for the coverage 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?

Specific verb ('test-parse') plus resource ('bank alert email') with a parenthetical clarifying intent (debug the alert parser). An agent can tell this is a diagnostic entry point distinct from siblings like save_alert_sources or list_bank_alert_guides, though the description never names those neighbors explicitly.

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 'Test-' prefix and 'debug the alert parser' imply a non-production, diagnostic context, which is genuine usage signal. However, it never states when to reach for this versus normal alert ingestion, whether it requires real email content, or that it has no side effects.

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