eco_feedback

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

No annotations present, so description carries full burden. Discloses non-authoritative nature (suggestions) and requires human review. Lacks details on output format or limitations, but output schema covers some behavioral aspects.

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?

Extremely concise: two short sentences plus a warning note. Purpose is immediately clear, no extraneous content.

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?

Covers input (failure analysis), output (suggestions), and usage note. Output schema handles return structure. Lacks mention of prerequisites like needing a prior failure analysis, but overall adequate for a suggestion tool.

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%, baseline of 3 applies. Description provides contextual examples but does not add significant meaning beyond parameter names and their schema descriptions.

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?

Clearly states the tool generates ECN suggestions from failure pattern analysis. Provides examples of suggestions (paste aperture changes, AVL updates) and distinguishes from siblings like ecn_create by emphasizing it is a suggestion stage.

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?

Indicates it uses failure analysis data and advises reviewing suggestions before creating formal ECNs, implicitly positioning it as a precursor to ecn_create. Could be improved by explicitly stating when to use versus alternatives.

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