Investments Get Security

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no behavioral context, such as side effects, authentication needs, or rate limits, beyond what the annotations provide. It does not contradict but also does not enhance transparency.

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 brief at two words, but this brevity sacrifices necessary information. It is not appropriately front-loaded with key details; instead, it is under-specified and fails to earn its place in a minimal definition.

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?

Given the lack of an output schema, the description should explain what the tool returns (e.g., security details). It does not, leaving the agent without critical context needed to interpret the response. The description is incomplete for a simple get operation.

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 provides no information about any of the four parameters. With only 50% schema description coverage, the tool relies on the description to compensate, but it offers no explanation for parameters like security_id or session_path that lack schema descriptions.

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 'Get security' is a tautology of the tool's name and title. It does not specify what a 'security' is in this context or what exactly is retrieved, failing to provide a clear purpose beyond what is already evident from the name.

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 given on when to use this tool versus its siblings such as investments_get_holding, investments_get_portfolio, or investments_search_securities. An explicit differentiation or context of use is entirely absent.

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