getBatchMarketCap

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, so the description's safety profile is covered. The description adds context that it's a batch operation using a specific API, enhancing transparency beyond annotations without contradiction.

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, 35 words, front-loaded with the action and resource. No redundancy or unnecessary detail. Every sentence provides 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?

Given the simple one-parameter tool with no output schema, the description is adequate but lacks details on response structure or data fields. It could be more complete by mentioning typical return values like market cap value and currency.

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?

Schema coverage is 100% with the description of 'symbols' matching the schema. The description adds 'multiple companies' and 'comma-separated' but these are already in the schema. No additional parameter semantics beyond repetition of schema info.

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 retrieves market capitalization data for multiple companies, using a specific verb 'Retrieve' and resource 'market capitalization data'. It distinguishes from siblings like getMarketCap (single) and getHistoricalMarketCap by emphasizing the batch nature and comparison capability.

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 comparing multiple companies' valuations simultaneously but does not explicitly state when to use this tool versus alternatives like getMarketCap (single) or getBatchQuotes. No exclusions or when-not-to-use guidance is provided.

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