Track a search

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

With no annotations, the description carries the full burden. It discloses the persistence behavior and the delta mechanism (new/reduced since last check). However, it does not explain side effects like storage duration, how to stop tracking, or authentication requirements, providing only partial 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 two short sentences with no redundant information, effectively communicating the core behavior. Every word earns its place.

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?

The description is adequate for distinguishing the tool and understanding its purpose, but it lacks details on parameters, return values, and state management. For a tool with 5 parameters and no output schema or annotations, the description is not fully complete.

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 only 20% (one parameter described). The description adds no parameter-specific semantics, leaving maxPrice, minBedrooms, name, and location undefined beyond their names. This fails to compensate for the low schema coverage.

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's function: persist a search and surface new or reduced listings on subsequent calls. This distinguishes it from one-time search tools like search_listings, providing a specific verb and resource.

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 usage for tracking searches over time with 'on later calls,' indicating repeated use. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to choose this over a one-time search.

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