add_place_alias

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

Beyond the destructiveHint and readOnlyHint annotations, the description reveals the idempotency nuance, the force condition, and the return value behavior (refreshed place dict with bounded snapshot catch-up). This adds meaningful operational context without contradicting the annotations.

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 front-loaded with the primary action, followed by concise but technically rich notes. It's longer than a single sentence but each sentence adds value for a mutating coordination tool.

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 place alias mutation with 3 params and an output schema, the description covers behavior, return, and a key race condition. It omits auth/error details but is sufficient given the schema and output schema.

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 has zero descriptions, so the description carries the burden. It explains the force parameter and implies place, but doesn't clarify alias format or place identifier semantics. It partially compensates but leaves some param details unspecified.

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 opens with a specific verb and resource ('Add an alias to an existing place'), clearly distinguishing it from sibling tools like add_place, delete_place_alias, and set_place_tags. The scope is unambiguous.

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 context for when the tool applies, such as the idempotency of duplicate alias insertion and the refusal on place acquisition by another identity unless force=True. It does not explicitly name alternative tools or exclusion criteria, but the conditions are concrete enough for an agent to decide.

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