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

Goes well beyond the annotations (which only cover read-only/idempotent/no-destructive semantics) by disclosing the 20-match cap, that the server cannot post into the conversation, that results are aggregator-scoped and may be incomplete, and that cars may already be sold. These are exactly the operational caveats an agent needs before presenting results to a user.

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?

Front-loads the usage trigger and then layers constraints in a single dense paragraph with no filler sentences. It is slightly long for a two-parameter list tool, but each clause carries distinct information.

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?

Although an output schema exists, the description usefully summarises the shape of results (newest 20 with price, verdict and link) and closes the main gaps an agent would otherwise hit: empty results before confirmation and aggregator-driven incompleteness. Nothing needed to call and interpret this tool is missing.

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 100%, and both the intentCode requirement and the 'since' semantics are already documented in the schema. The description restates them ('requires the intentCode; optional since returns only newer matches') without adding format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 cars found for a car watch') and ties it to the intent created via intent_publish_intent, which cleanly separates it from the sibling read tool intent_get_intent and from publish/withdraw. An agent can identify what this returns without opening the schema.

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?

Gives an explicit trigger ('use this when the user asks what AutoIsto has found') plus a precondition ('before the user confirms the intent there are no matches'), which tells the agent when NOT to expect results. It also names intent_publish_intent as the originating tool, so the workflow position is unambiguous.

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