get_company_profile

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

With no annotations, the description carries the full burden. 'Get' strongly implies a read-only operation and the Returns section describes the output, but the description does not explicitly state read-only behavior, potential errors, data freshness, or any rate-limit implications. This is barely adequate for a simple getter.

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 compact and well-organized with clear 'Args' and 'Returns' sections. Every sentence earns its place, and there is no redundant or filler content.

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 getter with an output schema available, the description covers the essential call contract: what the tool does, what input it needs, and what the return contains. No additional information is necessary for an agent to invoke it correctly.

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 0%, so the description must compensate. It does so effectively by defining 'ticker' as a stock symbol and providing concrete examples ('AAPL', 'MSFT'), which fully clarifies the only required parameter.

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 resource ('company profile and overview') and the verb 'Get', so an agent understands the tool's basic purpose. However, it does not explicitly differentiate this from sibling tools like get_quote or get_company_news, relying on the resource name alone for distinction.

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 when-to-use guidance or mention of alternatives is provided. The description explains the input and return value but does not help an agent choose between this and related tools such as get_quote or get_company_news.

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