ea_registry

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

There are no annotations, so the description carries the full burden. It discloses that this is a query over a catalog and that loading sources is avoided, which is useful. However, it does not disclose behavior such as how stale results are handled, whether refresh_if_stale is honored, or what the query syntax is. The refresh_if_stale=true default is a behavioral signal that is not explained.

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?

One sentence, front-loaded with the core action and the reason for using it. Every word earns its place.

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?

The tool has two parameters, no annotations, no output schema, and 0% schema coverage. The description is too minimal for an agent to know the query semantics, the refresh behavior, or the return shape. Given the sibling tools include refresh_ea_registry and ea_capabilities, more guidance is needed to avoid conflating them.

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 coverage is 0% and the description does not explain either parameter ('query' or 'refresh_if_stale'). The description only mentions the catalog query in general terms, so an agent cannot know what query format is expected, whether 'query' is a search string or filter object, or what refresh_if_stale=true actually triggers.

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 uses a specific verb ('Query') and resource ('compact EA catalog'), and adds a clear scoping reason ('without loading every .mq5 source into the AI context'). It conveys what the tool does, though it does not explicitly differentiate it from the sibling refresh_ea_registry or ea_capabilities.

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 description implies when to use this tool: when you want EA information without loading many source files. It does not explicitly state when to use alternatives, such as refresh_ea_registry (to refresh) or ea_capabilities (for capabilities), but the practical context is reasonably clear.

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