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

Annotations already declare readOnlyHint and openWorldHint, so the safety bar is low. The description adds a real behavioral caveat: statement rows vary by what Google publishes for the instrument, warning the agent that results are not guaranteed. It does not cover auth or pagination, leaving a small gap.

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?

Three tight sentences with the resource and scope front-loaded, followed by the availability caveat and the alternative-routing sentence. Every sentence earns its place and nothing is padded.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile. The description supplies purpose, routing, and an availability caveat, which is nearly complete for a single-parameter read tool.

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 description coverage is 100% for the single 'quote' parameter, so the schema already documents format. The description repeats the AAPL:NASDAQ example, adding no syntax or constraint beyond what the schema provides. Baseline 3 applies.

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 a specific verb ('Fetch'), resource ('annual and quarterly financial statement rows'), and source ('published on Google Finance'), plus a concrete quote-identifier format. It explicitly names sibling tools and what they serve, so the agent can distinguish this from google_finance_quote and google_finance_chart without opening a schema.

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?

Names two alternatives with their distinct purposes ('current quote fields' vs 'price timeline'), giving clear routing context. It stops short of an explicit when-to-use-this statement or any exclusion, but the implicit framing is strong.

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