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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: not which mode is active, what input shape selects diagnosis vs. ingestion, whether the tool mutates state, or what the output looks like. The dual-mode phrasing raises more questions than it answers.

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 sentence, which is appropriately sized, but the second clause is garbled ('ingests simulate results directly'), so the brevity comes at the cost of clarity rather than being disciplined 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 4-parameter tool with 0% schema coverage, no annotations, and no output schema, the description is substantially inadequate. An agent has no way to know how to invoke either of the two claimed modes or what the parameters should contain.

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?

All four parameters have empty schema descriptions (0% coverage), so the description must compensate, and it does not. Nothing in the text explains symptom_key's enum values, what observed_overshoot_pct/undershoot_pct measure, or how is_settled affects the audit.

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 verb 'Audits' plus 'operational pathologies' gestures at a purpose, but the opaque 'S-E-E-D Diagnostic Matrix' jargon and the elliptical second clause 'or ingests simulate results directly' leave the actual operation ambiguous. It never clearly states whether this diagnoses, validates, or imports data, and the only sibling signal is an indirect reference to simulate results.

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 explicit when-to-use guidance and no named alternative among the six sibling tools. The phrase 'or ingests simulate results directly' hints at a relationship with seed_system_dynamics_simulate, but it is phrased as a capability, not as a routing rule telling the agent which tool to pick.

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