fetch

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

The description mentions the return structure, which is helpful, but no annotations exist. It does not disclose whether the tool is read-only, idempotent, or any side effects, though a fetch is typically safe.

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 a single sentence with a clear return structure, making it concise and front-loaded. The prefix 'ChatGPT Deep Research:' is extraneous but does not hinder clarity.

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 existence of a closely related sibling ('cap_market_get'), the description should differentiate its use case. It also does not specify the format or source of the market ID, leaving gaps in context.

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 only parameter 'id' has no description in the schema (0% coverage) and the tool description does not explain what it represents or how to obtain it. This leaves the agent with minimal semantic guidance.

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 it fetches a market's details, with a specific verb and resource. However, it does not distinguish from the sibling tool 'cap_market_get', which likely has similar purpose.

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 is provided on when to use this tool versus alternatives like 'cap_market_get'. The description lacks context about prerequisites or scenarios.

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