get_symbol_profile

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

No annotations provided, but description transparently lists the rich return fields. Does not mention any side effects or constraints (e.g., rate limits), but for a read-only profile tool this is adequate.

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?

Two sentences: first states purpose, second lists key return fields. No redundancy, every sentence adds value.

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?

Output schema exists, so description need not detail return structure; it provides ample examples. Covers purpose, parameter, and return content sufficiently for an agent to select and invoke correctly.

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?

Input schema already fully describes the symbol parameter (type, example). Description adds no additional semantic information beyond the schema, so baseline score applies.

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?

Description uses specific verbs ('Get rich metadata and company profile details') and names many concrete fields (CEO, CUSIP, ISIN, etc.), clearly distinguishing it from sibling tools focused on specific financial data.

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?

Implied usage for obtaining company profile, but no explicit guidance on when to use versus alternatives like get_financials_overview or get_quote, nor any exclusions.

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