google_finance_context

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

No annotations are present, placing full burden on the description. It mentions 'normalized' results but does not explain what that means, nor does it disclose any behavioral traits such as data sources, pagination, or rate limits.

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 short (two sentences) but lacks substantive detail. It is concise but at the expense of clarity and completeness.

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 simple tool with one parameter and no output schema, the description still fails to provide sufficient context. It does not explain the structure of results or how they differ from other search tools, leaving gaps for the agent.

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 100% with a single parameter 'q' described simply as 'Search query'. The description adds no extra meaning beyond the schema, but since coverage is high, a baseline 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 says 'Google Finance context search' which is vague and not clearly differentiated from sibling tools like google_finance_search or google_finance_quote. The term 'context search' is ambiguous and doesn't specify what kind of results are returned.

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?

No guidance is provided on when to use this tool versus other Google Finance tools. There are many sibling tools with overlapping purposes, but the description gives no context for choosing this one.

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