company_esg

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

Describes the tool as researching and providing sources, implying read-only behavior. With no annotations, it could be more explicit about non-destructive nature and any data sources or limits beyond max_results.

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?

Well-structured with clear description and Args section. Some redundancy in listing ESG aspects, but overall concise and front-loaded.

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 return value explanation is not needed. Description covers all parameters and tool purpose adequately for the domain, though usage context could be stronger.

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?

Provides meaningful explanations for each parameter, especially output_format (answer vs structured) and max_results range. Schema coverage is 0%, so description adds significant value beyond schema.

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?

Clearly states it gets ESG and reputation information, listing specific aspects like sustainability, governance, controversies. Distinguishes from siblings like company_overview or research_company by focusing on ESG.

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 on when to use this tool vs alternatives. Does not mention when it is appropriate or when to avoid (e.g., for non-ESG queries).

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