Fetch ESG and sustainability data for a Yahoo Finance symbol to evaluate a company's environmental, social, and governance performance.
Yahoo Finance sustainability. Returns ESG and sustainability modules for a symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Yahoo Finance symbol such as AAPL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. The description does not disclose any behavioral traits such as read-only nature, error handling, rate limits, or whether the operation is destructive. Minimal disclosure beyond basic function.
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 concise at two sentences. It front-loads the key information and contains no filler. Every word earns its place.
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 tool has no output schema, the description should ideally provide more details about the returned ESG modules structure. It gives a high-level understanding but lacks specificity. Adequate for a simple tool 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 input schema has 100% description coverage for the single parameter 'symbol'. The description adds no additional meaning beyond the schema's description 'Yahoo Finance symbol such as AAPL'. It meets the baseline but does not enhance understanding.
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 the tool returns ESG and sustainability modules for a given symbol. The verb 'returns' and resource 'ESG and sustainability modules' are specific. Among many yahoo_finance_ticker_* siblings, this tool's focus on sustainability differentiates it effectively.
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 usage for obtaining ESG data. While it doesn't explicitly list alternatives, the purpose is clear enough that an agent should infer to use this tool when sustainability data is needed and other ticker tools for other data. A minor lack of explicit when-not-to-use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.