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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by noting profile fields are returned 'when available,' hinting at partial/optional data, but says nothing about auth, rate limits, or coverage across exchanges.

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?

Two tight sentences with the core action and payload front-loaded and the usage condition trailing. No filler, though it is not an exceptionally dense or structured definition.

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 single-parameter, read-only lookup with a rich output schema, the description covers what it fetches, what it returns, and when to call it. Nothing an agent needs to invoke it correctly is missing.

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% and the single quote parameter is documented with the same AAPL:NASDAQ example the description repeats. The description contributes no additional syntax or format meaning, 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?

States a specific verb (Fetches) and resource (Google Finance company profile) and enumerates the payload fields (description, CEO, employee count). It is distinguishable from sibling quote/ticker tools by its profile focus, though it does not name the siblings it differs from directly.

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?

Gives clear usage context: do a search first, or call it when the quote identifier is already known. It stops short of naming explicit alternatives (e.g. google_finance_quote) or exclusions, so the routing is good but not complete.

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