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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and data-scope are covered without the description's help. The description adds the payload contents, which is genuinely useful since there is no output schema, but says nothing about rate limits, data currency, or what happens for an unknown ticker.

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?

One compact sentence with the resource front-loaded and the fields listed colon-style. Nothing is wasted, though the field list is crammed in without punctuation structure that would help scanning.

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 one-parameter read tool with no output schema, the enumerated field list compensates reasonably well for the missing return documentation. Gaps remain around error behavior and ticker validity, but the core call path is unambiguous.

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% with a single well-documented parameter ('Stock ticker, e.g. AAPL'), so the baseline of 3 applies. The description adds no further meaning about ticker format, exchange prefixes, or case sensitivity beyond what the schema already states.

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 and resource ('Get a company's profile') and enumerates the returned fields (sector, industry, market cap, description, website). It is clearly distinguishable from the search-oriented siblings by its single-entity, ticker-keyed nature, though it never explicitly contrasts itself with search_companies or get_insider_profile.

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 when-to-use framing, no prerequisite (e.g. 'requires a valid public ticker'), and no named alternative such as search_companies for discovering a ticker first. The agent must infer the routing from the tool name alone.

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