publish_guide

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

No annotations are provided, so the description must carry the behavioral transparency burden. It states create/update but does not disclose update semantics (partial vs full), required permissions, or return values. This is minimal disclosure for a mutating 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?

A single, complete sentence that is front-loaded with the action and resource, with no redundant text 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?

The tool has 11 parameters and no output schema. The schema covers most parameters, but the description lacks guidance on when to use this vs sibling publish tools and does not explain update behavior. It provides a high-level purpose but misses behavioral and usage context that would make it 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 coverage is high (91%), yielding a baseline of 3. The description adds meaning by contextualizing the id parameter via 'Crea o actualiza' and explaining the related entity arrays via 'relacionando', which helps interpret those parameters.

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?

Description clearly states it creates or updates a guide and links POIs, Events, and Businesses. The verb 'Crea o actualiza' is specific, the resource 'Guía turística o temática' distinguishes it from sibling tools like publish_poi, publish_event, and publish_business.

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?

The description implies its use for guide-level aggregation but does not explicitly state when to use it vs alternatives or provide exclusions. No when-not guidance is given, so usage is inferred rather than explicit.

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