Señales de Quant Plus en lote

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

Goes well beyond the read-only/idempotent annotations by disclosing the auth model, the demo-key exception, and — critically — that only a curated universe yields signals and out-of-universe assets return `available: false` as a correct response rather than an error. That is exactly the behavioral context an agent needs to avoid misreading a legitimate result as failure.

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?

Five tight sentences, purpose first, then auth, then input format, then output semantics. Every sentence carries distinct information with no repetition or filler.

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?

With no output schema, the description compensates by explaining the `available: false` return case and framing it as expected. Auth, format, and edge-case behavior are all covered for a one-parameter batch 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 coverage is 100%, so the baseline is 3, but the description adds real meaning: coin identifiers like "bitcoin", not trading pairs, explicitly contrasting the convention with get_signal. It also clarifies that the 50-item cap is a request limit, not a limit on available signals.

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?

Opens with a specific verb+resource+scope: 'Señales de Quant Plus para varios activos en una sola llamada.' It is immediately distinguishable from get_signal and get_insight, and the batched nature of the call is stated up front.

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?

Explicitly states the prerequisite (Quant Plus pass) and a documented exception (demo public key works for bitcoin/ethereum, same as get_insight), and names get_signal as the contrasting tool whose input format differs. This is when-to-use plus when-not guidance, including alternatives.

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