ride_place_add

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

No annotations are supplied, so the description carries the full behavioral burden. '(dry-run)' hints at a preview mode, but the description never explains that the `confirm` flag actually commits the save, does not mention authentication via `token`, and says nothing about side effects or reversibility.

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 words is not conciseness but under-specification. There is no wasted text, but the sentence is far too small to carry the meaning needed for a six-parameter write 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?

With six undocumented parameters, no annotations, and no output schema, the description is drastically incomplete. An agent cannot determine auth requirements, what a dry-run returns, or how to actually persist the place.

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 0% across six parameters, so the description must compensate. It only loosely gestures at coordinates/name via the word 'place' and at the confirm/dry-run distinction; `token` and `address` receive no explanation at all.

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 name and description together give a verb and resource ('Save a place'), so an agent can roughly tell it creates a saved place. However, the parenthetical '(dry-run)' is ambiguous and partly at odds with the presence of a `confirm` parameter, and there is no differentiation from sibling tools like ride_place or ride_place_list.

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 gives no indication of when to use this tool versus ride_place, ride_place_list, or the many other ride_* siblings. Nothing is said about prerequisites (token/auth) or when the dry-run behavior applies, leaving routing entirely to the name.

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