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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral value beyond those annotations by enumerating what the response contains: company info, GF Score, GF Value, and sub-rankings, which helps set output expectations.

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 focused sentence with the action and key output fields front-loaded, followed by a concrete call example. Every part 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?

For a simple, read-only two-parameter lookup, the description plus schema and annotations provide everything needed to select and invoke the tool: required parameters, a working example, and the shape of the returned summary. No output schema is present, but the listed ranking fields give adequate context for correct use.

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%, with both symbol and _apiKey already documented in the input schema. The description's example repeats those parameters without adding new semantic detail, so the baseline score 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 states a specific action and resource: 'Get a GuruFocus stock summary/overview for a symbol.' It distinguishes itself from sibling GuruFocus tools by naming the proprietary ranking fields (GF Score, GF Value, sub-rankings), so an agent can identify this as the overview/summary tool rather than the price or insider tools.

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 intended use case is clear: when a stock symbol's summary/overview and proprietary rankings are needed. It does not explicitly name alternatives like gurufocus_price or gurufocus_gurus, nor does it give when-not-to-use guidance, but the context is strong enough to route an agent correctly.

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