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

With no annotations provided, the description carries full behavioral weight. It discloses the key side-effect boundaries: returns 'a binding USD price and quote_id (valid 15 min)', 'no execution yet and no credits consumed', and that execution later consumes credits. It also states the authentication requirement. This is excellent transparency for a quote operation.

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 three concise sentences with no filler. It front-loads the core purpose, then covers return values, validity, side effects, next-step routing, and authentication in a compact structure. Every sentence 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?

For a zero-parameter quote tool with no output schema, the description covers all essential context: what it returns, how long the quote is valid, that it does not execute, how to execute later, and what authentication is required. Nothing an agent needs to call this correctly or hand off to execute_quote is missing.

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 zero parameters, so per the calibration baseline this is a 4. The description adds no parameter-specific semantics because no parameters exist, but it does reference the quote_id produced by the tool, which is operationally relevant for the next step.

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 verb ('Request') and the resource ('ESG Intelligence Report'), and it explains what the report is for ('ESG intelligence synthesis for investment decisions'). It does not explicitly compare itself against the many quote_* siblings, but naming the specific deliverable is enough to separate it from the other quote tools.

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 gives explicit routing guidance: use this tool to get a quote, then 'Use execute_quote with the quote_id to run it.' It also states when not to proceed ('no execution yet'), making the quote-vs-execute flow clear. It does not mention other alternative quote tools, but the product-specific naming and the execute_quote handoff provide sufficient context.

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