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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no auth/permission requirements, no deduplication rules, no moderation or rate limits, no indication whether resubmission overwrites, and no statement of what happens on success. For a mutation tool this is a severe gap.

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?

One short sentence with no wasted words, but it is under-specified rather than concise: the brevity reflects missing information (scope, effect, required fields, sibling routing) rather than disciplined editing.

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 7 parameters (4 required), no annotations, and no output schema. The description supplies none of the missing context an agent needs — no submission semantics, no success/error behavior, no relationship to the get_locals_favorites read counterpart — leaving the definition inadequate for a 7-param write operation.

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 nominally 100%, which sets the baseline at 3, and the latitude/longitude fields do carry useful type guidance ('Send a number, not a string'). However, most schema descriptions just echo the field name (e.g., 'city': 'city'), and the tool description adds no meaning about what a valid category, city, or name should be, so it does not compensate for the thin schema text.

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 sentence 'Submit a locals' favorite' essentially restates the tool name share_local_favorite, which is tautological. It does convey a write/submit action on a 'favorite' entity, but gives no detail on what a 'locals' favorite' is (a place? a tip? a geo-tagged item?) or how it differs from siblings like save_listing or share_gem.

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?

There is no guidance on when to use this tool versus the many sibling write tools (save_listing, save_outing, share_gem, upvote_listing) or the read-only get_locals_favorites. The agent must infer usage entirely from the name.

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