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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds a unique behavioral trait: each line includes a quality assessment, which is useful context beyond the annotations. However, it doesn't detail return format or pagination, which is acceptable given read-only nature.

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 sentence, concise and to the point, with the main purpose front-loaded. No wasted words, though it could be slightly more structured with separate fields, but it's efficient.

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 the tool's moderate complexity, the description covers what data is returned and the unique quality assessment. With annotations indicating read-only and schema fully covering parameters, it's sufficiently complete, though it could mention the default quarters back behavior, but that's in 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?

Schema description coverage is 100%, so parameters symbol and quartersBack are fully documented. The description doesn't add extra meaning beyond the schema, but the baseline 3 is appropriate since schema covers everything.

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 it returns quarterly results including revenue, profit, balance sheet, and cash flows, plus a quality assessment of each line, which is specific and clear. However, it doesn't explicitly differentiate from siblings like get_earnings_deepdive or get_company_analysis, so it lacks sibling differentiation.

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 implies usage for retrieving quarterly KPIs but doesn't explicitly state when to use this tool versus alternatives like get_earnings_deepdive or get_company_analysis. Some context is given by listing the data fields, but no exclusions or alternative mentions.

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