Find a place to tag on Instagram or Facebook

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

Annotations are thin on operational detail, and the description fills the gap: no connected account needed, credit cost per lookup path (name search ~5-7 credits, FB link ~1, IG link/numeric id free), and that a place tag becomes public and is re-validated by Instagram at post time. The only reason it is not a 5 is that it does not say what happens when a name search returns no address-bearing Pages or how the candidate list is ordered.

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 and accepted input formats are front-loaded, and the return fields and credit model follow in a logical order with no filler sentences. It is a dense single paragraph, which makes the cost information slightly harder to scan than a short bulleted breakdown would be.

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?

There is no output schema, so the description carries the return contract itself and does so precisely (pageId, name, address, category, link). Combined with the cost model, the no-account requirement, and the hand-off to post_to_meta/schedule_post, an agent has everything needed to call it and act on the result.

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 100%, so the baseline is 3, but the description adds genuine meaning: it maps query forms to cost (an Instagram place link or numeric id costs nothing, a name search checks up to 5 Pages at ~1 credit each), which the schema does not convey. The `near` parameter and the limit ceiling of 8 are already covered by the schema, so those add nothing further.

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 ('Find a PLACE to tag') and enumerates what counts as a place (shop, cafe, restaurant, venue, landmark). It explicitly names the downstream siblings (post_to_meta, schedule_post) and the fields the output feeds, so an agent can distinguish it from generic search tools like search_instagram or list_meta_pages.

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 explicit input alternatives (name+city, Facebook Page link, Instagram place link, numeric id) and the conditions that select each, plus the required follow-up: 'These are matches to CONFIRM with the user'. It also routes results onward by naming the exact destination parameters (locationId, place, instagramLocationId).

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