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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the agent knows it's a safe read. The description adds that it returns specific fields and includes an example with an API key, which helps but doesn't cover rate limits or data freshness.

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 compact, with the main purpose and key fields front-loaded, followed by an example. No filler words; it earns its place.

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 absence of an output schema is mitigated by listing the return fields. The description covers what data is returned and how to call it. It doesn't explain pagination or result limits, but that's minor for a read-only data fetch.

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%, and the description provides an example call, which aids in understanding parameter format. However, it doesn't add meaning beyond the schema for 'symbol' and '_apiKey', so the 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?

The description clearly states the tool retrieves guru holding-change records for a symbol, listing the returned fields and providing an example. It differentiates from siblings like gurufocus_insider and gurufocus_summary through the focus on 'gurus' and 'holding changes', though it doesn't explicitly name which sibling to use instead.

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 fetching guru activity on a symbol, but provides no explicit guidance on when to use this versus alternatives like gurufocus_summary or gurufocus_insider. No exclusions or conditions are stated.

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