get_trade_screenshots

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, but it doesn't disclose whether screenshots are paginated, what happens if none exist, or authentication requirements. It adds the useful detail of returning both URLs and attachments, but leaves key behavioral traits unstated.

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 first sentence front-loads the purpose efficiently, and the example questions are compact and helpful. However, including two example questions is slightly verbose for a simple tool, adding marginal value without new information.

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 simple retrieval tool with no annotations or output schema, the description covers purpose and examples but omits behavioral details like error handling or return structure. It's adequate but leaves gaps an agent might need when invoking it.

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%, so the required trade_id parameter is fully documented with its format (UUID). The description only implies its use through examples and adds no syntax or format details beyond the 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?

States a specific verb (Get) and resource (chart screenshot URLs and image attachments) scoped to a specific trade. It's clearly distinguishable from siblings like get_trade_detail or get_trades, which cover broader trade data.

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 example questions ('Show the chart screenshots for trade...', 'Do I have any before/after chart images for this trade?') make the use case clear, and the trade_id scoping implies when to use it. However, it doesn't explicitly contrast with alternatives like get_trade_detail, which might also include screenshots.

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