get_tickers_jpy

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

No annotations provided, so description carries full burden. It only states it acquires data, omitting behavioral traits like read-only nature, idempotency, or side effects. Does not mention if any data is modified.

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 bracketed summary. No wasted words. Could be more informative but is appropriately concise.

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?

For a tool with 4 parameters, no output schema, and no annotations, the description is too minimal. It does not describe the ticker data fields (price, volume, etc.) or explain the difference between 'items' and 'ranked' views. Falls short of providing complete context.

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%, so description must add meaning. It mentions ranking by change rate/volume, which maps to sortBy and view parameters. However, it does not explain view ('items' vs 'ranked'), limit, or order. At least provides context for ranking capability.

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?

Description clearly states it retrieves tickers for all JPY pairs and supports ranking by change rate/volume. It contrasts with the singular 'get_ticker' sibling, though not explicitly mentioned. The verb '取得' (acquire) and resource '全JPYペアのティッカー一覧' (all JPY pair tickers list) are specific.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_ticker' or other analysis tools. The description implies it's for a market overview, but lacks when-to-use/when-not-to-use statements.

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