publish_poi

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

With no annotations, the description must disclose behavioral traits. It only says 'creates or updates' without explaining side effects, idempotency, whether the update requires an 'id', or any authorization needs. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence that conveys the core action and resource. There is zero wasted text; every word contributes to the message.

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 has 14 parameters, no output schema, and no annotations, a one-sentence description is incomplete. It does not explain return values, error conditions, or any post-publish behavior (e.g., whether the POI becomes immediately visible). The rich schema helps but does not compensate for the lack of behavioral context.

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 100%, so the baseline is 3. The description adds no parameter meaning beyond what the schema already provides, but the schema fully documents each parameter, including the optional 'id' for updates and coordinate examples.

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 action ('Crea o actualiza' = creates or updates) and the resource ('Punto de Interés (POI)'). It distinguishes itself from sibling publishing tools (blog post, event, business, guide) by targeting POIs specifically.

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 resource name (POI), making it clear when to use this over other publish tools. However, the description does not explicitly mention when not to use it, any prerequisites, or how it relates to list_pois or upload_media.

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