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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states read-only semantics, no mutation, fail-open behavior with mock fixtures when upstream is unreachable, and environment configuration requirements. This is unusually transparent and adds real operational context.

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?

Three sentences with no filler: first sentence states core purpose and output, second covers configuration/test mode, third confirms safety and failure behavior. Every sentence contributes actionable information and the most important identifying details are 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?

For a moderate-complexity read tool with no annotations and no output schema, the description covers purpose, data source, configuration, failure mode, and safety. It lacks an explicit return-format example or error-behavior details, but the listed output fields and fail-open note make it sufficiently complete for reliable invocation.

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 covers all four parameters with meaningful descriptions, so baseline is 3. The description adds some context around test_mode ('suitable for CI and demos', fail-open behavior) and frames ticker as commodity-exposed equities, but it does not significantly extend the schema's parameter documentation.

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 states a specific verb ('lookup') and resource ('Daloopa fundamentals for commodity-exposed equities'), lists concrete returned fields (revenue, opex, segment splits), and explicitly marks itself as read-only. This clearly distinguishes the tool from siblings like get_prices or mt_newswires_query.

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?

Provides clear context: it is for fundamentals of commodity-exposed equities, can be used without upstream credentials via test_mode, and is read-only. It does not explicitly name sibling alternatives or when-not-to-use conditions, but the usage context is strong enough for an agent to select it appropriately.

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