sc_security_news

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

With no annotations provided, the description must carry the behavioral disclosure burden. 'Get' implies read-only behavior and 'latest news summary' implies a return type, but the description does not disclose behavior around empty results, locale effects, staleness, or any operational constraints.

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, well-structured sentence that front-loads the action and resource. Every word contributes meaning, with no redundancy or filler.

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 relatively simple and has an output schema, so return values need not be described. Still, the absence of usage guidance, behavioral details, and locale semantics leaves some gaps for an agent invoking this tool in an unfamiliar context.

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 adds meaning to the primary parameter by saying the security is identified 'by ISIN'. However, schema description coverage is 0% and the locale parameter is not addressed beyond its schema default, leaving its purpose and accepted values under-specified.

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 states a specific verb ('Get'), a clear resource ('latest news summary'), and the key input ('by ISIN'), which makes the tool's purpose immediately obvious. It also distinguishes itself from siblings like sc_quote and sc_overview by targeting news rather than quotes or holdings.

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 implies when to use the tool: when a news summary for a security is needed. However, it provides no explicit guidance on when not to use it or which alternative sibling tool might be more appropriate in other scenarios.

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