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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the value of listing which specific profile fields are returned and confirms the single-ticker scope, providing useful context beyond the annotations. No contradiction with annotations.

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?

A single efficient sentence that names the tool's output fields and scope with zero wasted words. Every element contributes value.

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?

With one simple parameter, an output schema, and strong annotations (readOnly, idempotent, non-destructive), the description is largely complete for a lookup tool. It names the return fields and is scoped to a single ticker. Slightly more detail on the 'basic profile fields' could help, but this is adequate given the rich structured metadata.

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% (the symbol parameter is fully documented with pattern, length constraints, and example). The description references the profile fields but doesn't add syntax details for the parameter beyond what schemas already provide, 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 clearly states the verb ('Return') and resource ('company profile'), and lists the specific fields delivered (name, industry, exchange, market value, basic profile fields) for one ticker. It's defined at a single-ticker scope which differentiates it from market_symbol_search and market_quote, though it doesn't explicitly name sibling alternatives.

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 clearly applies to a single ticker (usage context implied), and the single-parameter symbol requirement implicitly signals this is a per-symbol lookup. However, it doesn't explicitly state when to prefer this over market_quote, market_fundamentals, or market_analyst_ratings, nor any exclusion conditions.

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