copy_ticks

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and writing a file is consistent with that. The description usefully warns that unbounded history is large and that all_history is mandatory in that case. It omits what happens when save_to is null (default path?), whether an existing file is overwritten, and rough output size — meaningful gaps for a write-to-disk tool.

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?

Front-loaded with the action in the first sentence and short overall. The second and third sentences restate the same all_history rule twice ('when dates are omitted' / 'required for that case'), which is mild redundancy but not harmful.

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 6 parameters at 0% schema coverage and no output schema, the description should explain the file destination, the format options, and the date semantics. Instead it covers only the all_history flag, leaving the agent to guess how the download is scoped and where the result lands.

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% across 6 parameters, so the description must carry the burden and largely does not. It only explains all_history and the date-omission case; format values, save_to default location, and the accepted date string format for date_from/date_to are entirely undocumented in both schema and description.

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?

States a specific verb and resource with destination: 'Download ticks to a file.' That clearly separates it from sibling readers like symbol_tick and from copy_rates. It does not explicitly name the alternatives it supersedes, so it stops short of a 5.

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 gives a conditional rule ('Set all_history=true when dates are omitted') but it is a parameter rule, not when-to-use-this-tool-vs-alternatives guidance. There is no indication of when to prefer this over symbol_tick or copy_rates, or any prerequisite about a terminal/connection being active.

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