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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds value by listing the return fields, but it does not disclose behavior for invalid symbols, error responses, or any rate limiting. This is adequate given the annotations, but not richly transparent.

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, well-structured sentence that immediately states the primary action ('Fetch FMP company profile for a ticker symbol') followed by a list of included data fields. Every word contributes meaning; there is no redundancy or fluff.

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 one-parameter read-only tool with rich annotations and no output schema, the description adequately covers the expected return content by listing the key fields. However, it omits edge-case behavior (e.g., unknown ticker) and return format details, which slightly reduces completeness.

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 provides only a bare 'symbol' string parameter with no description, leaving the description to carry the meaning. The description explicitly labels it a 'ticker symbol', which effectively clarifies the expected input. With a single parameter, this level of explanation compensates for zero schema coverage.

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 tool fetches an FMP company profile for a ticker symbol and enumerates the data fields included (sector, industry, description, CEO, etc.). It is specific and unambiguous, though it does not explicitly contrast itself with the sibling tool entity_profile, which may serve a similar purpose.

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?

The description implies usage when a user needs fundamental company profile data for a specific ticker, but it provides no explicit guidance on when to choose this tool over alternatives like entity_profile or quote. There are no exclusion criteria or mention of alternate tools, so usage guidance remains implicit.

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