fmp_balance_sheet

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

No behavioral traits are disclosed. The description does not mention side effects, permissions, rate limits, or output format. With no annotations to supplement, the description entirely fails to inform the agent about the tool's runtime behavior.

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 extremely short, which is concise, but it is too brief to be useful. It does not earn its place because it adds minimal information beyond what the tool name implies. The structure is a single phrase without any elaboration.

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?

The description is incomplete relative to the tool's context. It does not mention the output schema, the nature of the data, or any usage constraints. Even with a simple schema, the description fails to provide essential information for the agent to effectively invoke the tool.

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 description does not explain any of the parameters (symbol, limit, period) or their meanings. Given the schema has 0% description coverage, the description should compensate by elaborating on parameter roles, but it does not, leaving the agent to guess.

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 'Balance sheet statements' identifies the topic but does not clearly state the tool's action (e.g., retrieves, fetches, lists). It is a noun phrase rather than a clear verb-driven purpose, leaving ambiguity about what the tool actually does.

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 provides no guidance on when to use this tool versus alternatives (e.g., income statement or cash flow tools). It does not mention parameters, typical use cases, or any decision criteria, leaving the agent without context for selection.

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