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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description does not need to restate safety. The word 'loaded' hints at a pre-built snapshot, but it is too vague to disclose meaningful behavior such as data freshness, failure modes, or coverage limits.

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 a single short sentence with the action and resource front-loaded. It contains no filler or redundant restatement of the input schema, making it easy for an agent to scan.

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 no output schema, the description leaves the contents of a 'company profile' undefined, so an agent cannot know whether it returns identifiers, fundamentals, ownership, or summary data. Given the large sibling family, this missing specificity is a significant gap for a tool whose only parameter is already fully documented.

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?

The schema fully documents the single ticker parameter and even gives 'NVDA' as an example, so schema coverage is 100%. The description only restates 'by ticker' and adds no format, alias, or usage detail beyond the schema, 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 states a specific action ('Return') and resource ('curated company profile') keyed by public ticker, so an agent can tell it is a lookup tool. However, it does not distinguish company_ticker from adjacent siblings such as company_enrich, company_search, or equities_ticker, and the qualifier 'loaded' is ambiguous.

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?

No guidance is given about when to use this tool instead of the many sibling company/equities tools, and no alternative tools are named. The phrase 'curated company profile' hints at a use case but does not establish selection criteria or exclusions.

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