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 behavioral effects of each action (offer/counter opens/advances negotiation, decline/opt_out ends it) and notes token authorization without scope. It does not mention post-action responses or reversibility, but core behavior is well covered.

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 concise and front-loaded, with three dense sentences that each add value: the primary use case, the action semantics, and the auth model. There is no redundancy or fluff.

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?

Given the tool's modest complexity (3 parameters, no output schema), the description covers essential context: purpose, action semantics, token source, and auth. It does not discuss return values or failure modes, but those are not critical for this straightforward action tool.

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%, so the baseline is 3. The description adds meaning by specifying that price is required only for offer/counter and explaining that accept agrees to the buyer's current offer, which clarifies the purpose of parameters beyond their raw schema descriptions.

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+resource: 'respond to a broker's acquisition inquiry' and distinguishes it from siblings by noting the 'Owner-agent path' and autonomous token-based flow. It also enumerates distinct actions (offer/counter, accept, decline/opt_out), giving a clear scope.

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?

It provides clear context for when to use: when you have a broker inquiry token from an outreach email and want to respond without email/magic-link. It implicitly contrasts with alternatives but does not explicitly name sibling tools, so guidance is useful though not exhaustive.

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