Get all deals

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

No annotations provided, so description should cover behavioral aspects. It merely says 'Get all deals' without mentioning pagination, sorting, rate limits, or authentication. Schema has some parameters but description adds no transparency.

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 very short (two sentences) but front-loads the HTTP method and purpose. However, it is under-specified and could include more useful details without being verbose.

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 annotations and no output schema, the description lacks context about deal statuses, result structure, and relationship to other entities. It is insufficient for a complex tool with many parameters.

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?

Description adds no information about parameters beyond the schema, which has partial descriptions (e.g., sort, limit). For parameters like 'statusId' or 'tags', no extra context is provided.

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 retrieves deals via GET endpoint and mentions the resource 'all deals'. It distinguishes from siblings like 'weeek_get_a_deal' which retrieves a single deal.

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 on when to use this tool vs alternatives like 'weeek_get_a_deal' or other list tools. No prerequisites or exclusions mentioned.

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