earnings_trend

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine value by disclosing that a computed classification (accelerating/steady/decelerating) is returned, but it says nothing about history depth, missing-data behavior, or cost of a call.

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 dense sentence with the return content front-loaded and no filler. It is efficient, though the absence of any parameter clause means the brevity is partly achieved by omission rather than by tight writing.

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 does a reasonable job naming the return fields, which is the main burden here. However, for a two-parameter tool with zero schema documentation, omitting the quarters window leaves the agent unable to control or predict the result span.

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 the description must carry parameter meaning, and it does not mention either parameter. The 'quarters' input with its default of 8 is undocumented anywhere, and the symbol's expected format (ticker, exchange suffix) is left entirely unspecified.

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 the specific resource (quarterly sales/profit/margin/EPS) and the derived signal (year-on-year growth plus acceleration state), which is more informative than the bare tool name. It does not explicitly differentiate itself from financial_statement, which is the nearest sibling and likely overlaps.

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?

There is no guidance on when to pick this over financial_statement or company_overview, nor on prerequisites such as whether the symbol must be a listed equity. Usage can only be inferred from the words 'quarterly' and 'trend'.

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