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

No annotations are provided, so the description carries the full burden. It uses 'Get' to imply a safe, read-only operation and enumerates the returned data (offers, messages, unread count), indicating no side effects. It doesn't disclose edge cases or error conditions, but for a simple status getter this is adequate.

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 one compact sentence with a hyphen-separated list of contents, followed by a clear use case. Every phrase adds value and the most important action ('Get') is front-loaded.

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 tool is simple with one parameter and no output schema, so the description doesn't need to be verbose. It specifies the core outputs (offers, messages, unread count) and the intended use case. It could mention that it requires an existing session, but the schema already states that; overall it is sufficiently complete for a tool of this complexity.

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?

The schema fully documents the single 'session' parameter as a 'Session hash' (100% coverage). The description does not add extra parameter context, but the baseline of 3 applies because the schema is self-sufficient.

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 verb 'Get', the resource 'current deal status', and specifics: offers received, messages exchanged, unread count. This distinguishes it from sibling tools like cars_session_message or cars_session_reply, which focus on messaging rather than overall deal status.

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 explicitly says 'Use to check if the dealer has responded,' providing a clear when-to-use scenario. However, it lacks exclusions or mention of alternative tools, so it doesn't fully differentiate in both directions.

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