ratios

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description only restates the output concept ('financial ratios') without adding behavioral context such as the ratio categories covered, data source, time period, or how open-world results are organized.

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 five words and front-loads the essential concept immediately. Every word earns its place, and there is no 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 should explain what the agent will receive; it does not. There is no mention of the ratio set, formatting, or any caveats, leaving an agent to discover the output contract only after invocation.

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%, and the symbol parameter is documented as 'IDX ticker', so an agent knows what value to supply. The description adds no extra parameter context, but none is necessary given the complete schema.

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 states the resource ('financial ratios') and the subject ('a company'), so an agent can broadly infer it returns ratio data for a ticker. However, it has no explicit verb like 'calculates' or 'retrieves', and it doesn't clearly differentiate from siblings such as financials or keystats beyond the word 'ratios'.

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 given about when to choose ratios over financials, technicals, keystats, or quote. There are no exclusions, prerequisites, or conditions, so the agent must guess which tool fulfills a ratio-related request.

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