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

No annotations are provided, so the description carries the full burden, and it does signal read-only behavior via "(GET)", which is useful safety context. However it says nothing about result size or pagination for "full message history", nor about the failure path implied by the notification_message parameter. Adequate but with real gaps for an unannotated tool.

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, zero filler, with the action stated first and the routing condition second. 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 read-only GET with fully documented parameters and no output schema, the description covers purpose and sequencing well enough to invoke correctly. It could do slightly more on what the returned thread contains and whether the history is paginated, but no critical invocation detail 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 description coverage is 100%, so the schema already explains advert id, seller user_id with .json suffix, and the fallback message. The description adds no parameter-level meaning beyond that, which is the baseline 3 case when the schema does the heavy lifting.

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?

"Read full message history for one chat thread (GET)" gives a specific verb (read), a specific resource (one chat thread's full message history) and scope (single thread, full history). It is clearly distinguishable from list_messages, send_reply and start_chat without opening any 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?

"Use after list_messages when the user picks a vendor thread" states the prerequisite tool and the triggering condition explicitly. It does not cover when not to use it (e.g. thread already loaded) or name a fallback, but the routing guidance is concrete.

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