product_catalog_latest

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds crucial behavioral details: large CSV (~150 MB, binary/octet-stream), presigned URL expires in ~300s, and describes response structure. Adds value beyond annotations.

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?

Well-organized: purpose, response shape, data details, scope clarification, expiry warning, link to spec. Slightly lengthy but every sentence adds value. Acceptable for a complex tool.

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 no output schema, the description fully explains what the tool returns (response shape, CSV columns, expiry). Also clarifies scope and provides API reference. Completely adequate for an agent to use.

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?

No parameters; schema coverage 100%. Description adds no parameter info but provides complete context on response shape and data columns, which is sufficient.

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 a presigned S3 URL for the latest public marketplace app-catalog snapshot. It distinguishes from siblings by specifying it's the whole marketplace, not vendor-specific. The response shape and constraints are clearly outlined.

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 that this returns public marketplace data (all vendors) and not your own apps or product/pricing structure. Mentions presignedUrl expiry and prompt download. Could explicitly name alternative tools for vendor-specific data, but strong guidelines.

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