company_fundamentals

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get', which implies read-only, but it does not explicitly state that no data is modified, nor does it mention data source, coverage, rate limits, or any other behavioral traits. It adds minimal context beyond the operation itself.

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 two sentences with no filler, and the purpose is front-loaded. The Args line is structurally redundant with the schema but earns its place by adding Indian-market context and examples that the schema lacks.

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 tool with an output schema, the core call contract is present: the purpose is clear and the ticker parameter is well illustrated. However, the absence of usage routing and explicit behavioral disclosure leaves the description adequate but not fully complete.

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 0% description coverage and only names the property 'ticker'. The description compensates by specifying 'Indian stock ticker symbol' and giving concrete examples like 'RELIANCE', 'TCS', and 'INFY', which is exactly the practical guidance an agent needs to supply the parameter correctly.

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 a specific verb ('Get') and resource ('fundamental analysis data'), and the phrase 'fundamental analysis' helps differentiate it from siblings like technical_analysis and stock_quote. It does not enumerate what specific fundamentals are included, but the core purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as technical_analysis, analyst_recommendations, or stock_quote. No context is given about whether this is for long-term investing, what data it covers, or when a sibling would be more appropriate.

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