get_recent_deals

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

With no annotations provided, the description should fully disclose behavioral traits. It does not state whether the operation is read-only, any side effects, sorting order, or what 'recent' means. The only behavioral hint is that the tool returns deal IDs, but transparency is insufficient.

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 concise (13 words) and front-loaded with the action. Every word serves a purpose, but it sacrifices some clarity for brevity. For a simple tool, this is appropriately sized, though a bit more detail could improve it.

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 lack of output schema and annotations, the description fails to provide complete context. It mentions deal IDs but not the full return structure. The agent lacks information on pagination, default limit behavior, and what fields are returned. The description is minimal and incomplete for effective tool selection.

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 input schema already describes both parameters (limit and company_id) with 100% coverage. The tool description adds no additional meaning or guidance for the parameters, so the baseline score of 3 is appropriate.

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 states the verb and resource ('Get recent deals') and provides a specific use case ('to find deal IDs for deletion or review'). However, it does not differentiate from the sibling tool 'list_deals', which likely returns all deals. The purpose is clear but not fully distinguished from alternatives.

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 description implies when to use (for deletion or review) but does not explicitly state when not to use or mention alternatives. The sibling 'list_deals' is an obvious alternative for general listing, but no guidance is provided. The usage context is hinted but not fully clarified.

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