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

No annotations are provided, so the description carries the full burden. It does disclose that the data is a 'current' (point-in-time) profile and what categories it contains, but says nothing about authentication, rate limits, freshness/latency, or failure behavior for an invalid symbol.

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 front-loaded sentence with no filler; the resource and payload scope come first. It is arguably too terse to carry the sibling-differentiation burden, but nothing in it is wasted.

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 simple read-only lookup with a fully documented two-parameter schema, the description is minimally adequate. It is missing only the sibling disambiguation (get_stock_info vs. this tool) and any note on output fields, which, with no output schema present, would have been useful.

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%, so both the symbol format examples and the 'type' disambiguation parameter are already fully documented in the schema. The description adds no additional parameter meaning, making the baseline 3 the correct score.

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+resource ('Get the current company profile') and enumerates the content scope ('listing and industry information'). It does not, however, differentiate itself from the sibling get_stock_info, which a caller could reasonably confuse it with.

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 guidance on when to use this tool versus the many sibling lookups (get_stock_info, get_industries_tree, get_industry_peers). No prerequisites, no exclusions, no alternatives named — the agent must infer usage entirely from the name.

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