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

Annotations already establish a non-destructive, closed-world create operation, and the description adds genuinely useful lifecycle context that annotations do not carry: the ad stays live 30 days, is renewable/closable, and sellers respond by email. It does not state what the call returns or whether any auth/membership is required, so it is strong but not complete.

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 short sentences, no filler, with the core action front-loaded and the post-creation behavior following. Every clause 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?

For a create tool with no output schema and light annotations, the description covers the important non-obvious behavior (durability, renewal/close, response channel). The main omission is what the caller gets back (e.g., ad id/URL) and any posting limits.

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 100%, including per-field examples and the 2000-character limit, so the schema carries full weight here. The description adds no parameter-level detail beyond the schema, matching the baseline of 3 for well-documented schemas.

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 a specific verb and resource ('Post a wanted ad on NeedToFind') plus the intent ('something the user is looking for'), which cleanly separates it from siblings like respond_to_want and search_wants. It stops short of naming any sibling explicitly, so it falls just below the top band.

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?

Usage is implied by 'something the user is looking for' but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as respond_to_want or set_alert for related goals. Adequate but leaves routing to inference.

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