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

The readOnlyHint:false annotation already marks this as a write. The description adds genuinely useful context beyond that: "Live immediately, like anything a person posts" discloses there is no draft or moderation state, and the required services:write scope is an explicit auth prerequisite.

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?

Three short, front-loaded sentences with no filler. The core purpose leads, followed by behavioral context and the scope requirement.

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 5-parameter mutation with no output schema and thin schema coverage, the description covers auth and the immediate-visibility behavior but says nothing about the fields being set (rate, notes, dry_run) or what a successful call returns. Partially complete.

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 only 20% (just category_id: "From list_categories"). The description adds no meaning for name, rate, notes, or the ambiguous dry_run flag, so four of five parameters are undocumented in both places.

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?

States a specific verb+resource ("Create a service listing") and clarifies what a listing is with the parenthetical "the work they offer." The verb "Create" implicitly separates it from update_service and list_services, though no sibling is named explicitly.

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 the verb — create a new listing — but there is no explicit when-to-use or when-not guidance, nor any pointer to update_service for modifying an existing listing. 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.