getLightChart

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds minimal behavioral context beyond stating the data scope (essential charting info), not elaborating on rate limits, authentication, or response structure. With strong annotations, the description's additional value is moderate.

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?

Two concise sentences that front-load the purpose and immediately state the data provided. No redundant or unclear phrasing. Every word serves a purpose.

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 no output schema, the description adequately hints at return data (date, price, volume). It does not specify if the result is a list or single record, but for a simplified chart tool this is sufficient. The tool's simplicity is well communicated, though it could briefly contrast with getFullChart for completeness.

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?

Input schema has 100% coverage with descriptions for all three parameters. The description does not add meaning beyond what the schema already provides (e.g., confirming that from_date and to are optional, or clarifying default date ranges). Baseline of 3 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 accesses simplified stock chart data and lists the specific data fields (date, price, volume). It uses the term 'simplified' to distinguish from more comprehensive chart tools like getFullChart, making the purpose precise and distinct from siblings.

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 suggests use for 'tracking stock performance with minimal data and creating basic charts,' implying a lightweight scenario. However, it does not explicitly state when not to use it or mention alternatives (e.g., getFullChart for more detail), leaving the agent without clear exclusion criteria.

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