discover_markets

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The phrase 'Sólo se opera el actual' adds a behavioral constraint, but it is ambiguous (operated/traded) and does not explain return behavior, dynamic data, or pagination. The description adds little reliable context beyond what annotations already supply.

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?

The description is extremely short and each fragment is compact, but the structure is telegraphic and missing a clear sentence. It is concise, but the under-specification makes it closer to a note than a tool description.

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?

Given the two optional parameters, lack of output schema, and sparse description, the agent lacks enough information to correctly call the tool and interpret results. The meaning of 'windows', 'asset', and 'Sólo se opera el actual' is left ambiguous, making the description incomplete for reliable use.

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%, so the description must compensate. It does mention 'windows: 1..6', which gives a valid range for the windows parameter, but it completely omits any meaning for the 'asset' parameter. With two parameters and no descriptions, this is insufficient.

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 'Mercados 5m del intervalo actual y próximos' indicates the tool relates to 5-minute markets for the current and upcoming intervals, but it is a noun phrase with no explicit verb like 'returns' or 'lists'. It gives some scope but does not clearly distinguish from sibling tools such as get_market_snapshot or get_market_context.

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 guidance on when to use this tool versus alternatives. The description never mentions conditions, prerequisites, or sibling tools, leaving the agent to infer the appropriate context from the name alone.

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