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

With readOnlyHint already declaring a safe read operation, the description adds substantive behavioral context: it defines the annual dividend treatment and explains the preferred-share/assetType edge case. It still omits data freshness or error behavior, so it is not fully comprehensive.

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 front-loaded and compact for the amount of return-field and edge-case detail it conveys. The bilingual restatement is somewhat duplicative and the parentheticals make it dense, but nothing is clearly extraneous.

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?

Because there is no output schema, the description carries the burden of describing return content, and it covers profile fields, valuation metrics, dividend semantics, and preferred-share handling. Remaining omissions such as data freshness or currency details are minor for this read-only profile tool.

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%, so the symbol format and example are already documented in the input schema. The description does not directly define the symbol parameter, and its 5-digit preferred-share note concerns output classification rather than adding clear input syntax beyond the schema.

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 names the resource and enumerates the profile plus latest valuation fields the tool returns. It is specific enough to separate it from unrelated siblings like get_historical_prices, but it does not explicitly contrast with overlapping siblings such as get_quote or get_key_metrics_latest.

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?

There is no explicit when-to-use or when-not-to-use sentence, and it does not name alternatives among the many sibling tools. The field list implies the tool is for company profile and latest valuation lookups, but selection between this and get_quote/get_key_metrics_latest is left to inference.

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