get_stock_details

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the side-effect profile is covered. The description adds a useful contextual trait: the data is Trade Republic's own editorial company details rather than user data. However, it does not discuss availability, staleness, or response behavior, so the added value is modest.

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, front-loaded sentence with no filler. The parenthetical efficiently enumerates the return content, and every word contributes to the tool's meaning.

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 tool is simple with one parameter, and annotations cover the safety profile. However, with no output schema, the description's content list is the only return-value guide, and the lack of usage or parameter detail leaves some ambiguity. The parenthetical helps but does not fully compensate for those gaps.

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 has one required ISIN parameter with 0% description coverage, and the description does not explain its format, validity, or exact role beyond tying it to 'a stock.' Since the schema only supplies the title 'Isin', the description needed to compensate for the missing parameter documentation and did not.

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 identifies the resource ('company details for a stock') and the content it contains ('description, key figures, analyst ratings'), so an agent can tell what the tool does. It does not use an explicit retrieval verb and does not contrast with similar siblings like get_instrument or get_quote, so it stops just short of a top score.

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 get_quote, get_instrument, or get_news, nor any mention of prerequisites or context. The phrase 'stock details' implies a use case, but with 21 siblings an agent is left to infer the appropriate choice.

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