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

With no annotations at all, the description carries the full load and does disclose the important traits: this is a mutating publish with a real side effect (guides in that city get notified and will apply with quotes), it requires a configured Authorization: Bearer token and returns setup guidance otherwise, and confirmation must precede it. It does not cover the return value, whether a demand can be cancelled or edited afterward, or duplicate-post behavior.

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?

Four sentences, front-loaded with what the tool does, then post-publish flow, then the auth requirement, then the confirmation rule. Every sentence contributes; the middle sentence on the application flow is slightly long but is genuinely useful context for the agent.

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 an 8-parameter mutation with no annotations and no output schema, the description covers auth, side effects and preconditions well. The remaining gap is the return shape (e.g., a demand ID or confirmation payload) and any edit/cancel path, which are nowhere stated since no output schema exists.

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% with per-parameter descriptions, defaults and constraints, so the baseline is 3. The description adds a prioritization layer by singling out city, travel date, budget and headcount as fields that must be confirmed with the user before calling, which is meaning beyond the schema.

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 and resource (publish a 'find a guide / custom itinerary' travel demand) and then describes the resulting pipeline: the platform notifies guides in the target city, guides apply with quotes, the user reviews applicants in the app. That is unmistakably different from the retrieval-only siblings (search_guides, get_guide_detail, search_lines, get_line_detail).

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?

Gives an explicit precondition and an explicit prohibition: confirm city, travel date, budget and headcount with the user first, and do not publish casually without confirmation. It stops short of naming an alternative (e.g., browse with search_guides instead when the user is only exploring), so not a full 5.

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