fmp_profile

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

There are no annotations, and the description only lists data fields; it does not disclose side effects, permissions, operational constraints, or output behavior meaning.

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 clear sentence adding compact field list to the description; no filler or repetition.

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?

An output schema is present, and the tool is a simple lookup/profile tool, but the description lacks behavioral detail such as what exactly is returned, error conditions, or where input comes from.

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 JSON schema fully defines the single property ('symbol' string). The description does not restate its meaning, but with only one param and schema coverage at 100% this is acceptable.

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?

Description names the domain (company profile) and enumerates contained fields, but uses a noun phrase with no fetch/retrieval verb and does not differentiate this historical/fundamental data tool from siblings.

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 provided for when to use this tool versus sibling fundamental data tools, nor any exclusions or alternative context.

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