list_deals

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the sort order and the AND-combination semantics of filters, which is genuine added context, but it says nothing about pagination, the default limit of 20, or result volume — relevant for a list tool over an open-world dataset.

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?

Two sentences, no filler, with the ordering and filter behavior front-loaded. Nothing is wasted and nothing is buried.

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?

An output schema exists and read-only annotations cover safety, so return values needn't be described. Still, for a 5-parameter list tool with zero schema documentation, the description leaves meaningful gaps: pagination, the limit ceiling, and the meaning of the ambiguous id filters.

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 description coverage is 0% across 5 parameters, so the description carries the burden and largely does not meet it. It only establishes that all filters are optional and ANDed together; it never explains whether stage_id is an opaque string id, whether assigned_by_id means "assigned to" or "assigned by," or that title_contains is a substring match.

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 and resource ("List deals") plus a default ordering ("newest first"), which is enough to separate it from get_deal (single record) and list_deal_stages (different resource). It never names a sibling or clarifies why you'd pick this over a search tool, so it falls short of a 5.

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?

"Filters are optional and combined with AND" gives real invocation context — you learn you can call it with zero arguments and that multiple filters narrow rather than broaden. However there is no when-to-use vs. alternative guidance, no mention of pagination strategy, and no indication of what an unfiltered call returns.

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