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

Annotations already declare a non-destructive, idempotent write, and the description reinforces that with concrete retry semantics: reusing an ID with different input is rejected. It also adds auth requirements (account plus explicit consent) and notes the response carries data and source/freshness metadata, which annotations cannot convey.

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?

Purpose is front-loaded and the requestId rule is stated compactly, but the trailing units sentence ('ft, kt, s, F, mi; directions FROM') appears to be copy-pasted global boilerplate that carries no meaning for a save operation.

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 mutation tool the safety profile is well covered by annotations plus the consent statement, and the return metadata is flagged. The critical gap is the nested place schema: with no output schema and 0% parameter coverage, an agent has no guidance on the fields it must construct.

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 0% and the single body parameter hides a nested place object with nine undocumented fields (lat, lon, kind, name, activity enum, etc.). The description explains the requestId contract well, but says nothing about what belongs in the place object, so an agent still cannot populate the payload from the description.

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 ('Save a place or favorite'), which is clearly distinct from read tools like get_my_place or list_my_places. However, it never differentiates from the write sibling update_my_place, so an agent must infer which write path applies when the place already exists.

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 conditional guidance on the requestId (use a fresh unique ID, reuse it on retry) and states the prerequisites (Gillby account plus explicit account consent). It does not say when to prefer this over update_my_place or how it relates to save_my_trip, so routing among the write siblings is left to inference.

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