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

Annotations already declare this is a non-destructive, non-open-world write, and the description adds genuinely useful context: submissions are stored for the hub team, NEVER published, and should contain no personal data. It says nothing about idempotency or what happens on repeated submissions, which matters given idempotentHint=false.

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?

Short, front-loaded, and every sentence adds something (purpose, enum values, length, storage behavior, privacy). The 'kind: offer or missing' clause duplicates the schema enum, a small redundancy, and the telegraphic style is slightly terse.

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?

With an output schema present, annotations supplied, and full parameter coverage, the description only needed to explain the submission's intent and handling, which it does. The main residual gap is repeat-submission or rate behavior, which is minor for this 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 kind, text, lang, and contact_url are all already documented. The description restates the enum values and character range and adds only the 'no personal data' constraint on text. Baseline 3 is appropriate 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?

The description states a concrete action and resource: submit an offer or a 'missing' report to the hub, which is clearly distinct from the retrieval siblings get_listing and search_listings. It does not explicitly name those siblings, so differentiation is implied by the verb rather than stated.

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 gives clear triggering contexts: you have something to offer, or you searched and found nothing. That second clause implicitly ties it to a prior search, but there is no explicit exclusion or named alternative for edge cases.

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