getStockDaily

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

No annotations exist. The description is vague about what 'daily trading information' includes (e.g., open, close, volume) and whether data is historical or real-time. Critical behavioral traits like update frequency or data range are missing.

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 a single concise sentence with no redundant words. It is front-loaded with the core action and scope, fitting the criterion of every sentence earning 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?

No output schema exists, so the description should explain the return value. 'Daily trading information' is too vague; it doesn't specify fields, date range, or whether it returns a list of all stocks. Richer context is needed for a tool with 0 parameters and no output schema.

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?

The input schema has zero parameters, so schema description coverage is 100% (no parameters to describe). With no parameters, the description need only confirm no filtering; it does this implicitly. Baseline 4 is appropriate.

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 clearly states the tool retrieves daily trading information for all listed stocks on TWSE. It uses a specific verb ('Get') and a resource ('daily trading information for all listed stocks'), distinguishing it from siblings like getStockDayAvg.

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 guidance is provided on when to use this tool versus alternatives like getStockDayAvg, getMarketIndex, or other daily stock data tools. The agent must infer usage 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.