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

Annotations already mark the tool as read-only and non-destructive, and the description adds useful behavioral context beyond that: the search is backed by Bing, results are meant to be passed into create_post, and the tool requires a Company Page account with a follower threshold. This is substantive context and does not contradict 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 compact and front-loaded: it states the core function first, then the downstream usage, then the prerequisites. Every sentence adds necessary information and there is no filler.

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 description explains purpose, downstream use, and prerequisites, and the 'urn + displayText' hint partially compensates for the missing output schema. However, with no output schema and no parameter-level documentation, the agent is left to infer the exact meaning of query and accountId and the full shape of the response. It is adequate for selection but not fully complete for invocation.

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%, so the description must explain the two required parameters, but it only weakly implies that query is the search term. accountId is never explicitly tied to the Company Page account or explained as an identifier. The description mentions the output fields urn and displayText, but does not clarify how they relate to the input parameters.

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 description names the specific operation: 'Search Bing geo locations' for LinkedIn Company Page organic targeting. It also differentiates the tool from sibling search tools like linkedin_search_organizations and linkedin_search_people_mentions by pointing to a distinct resource type, geo locations, and by explaining how results flow into create_post.

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 concrete usage context: use this tool to obtain geo-location targets for LinkedIn Company Page posts via create_post. It also states prerequisites including the need for a Company Page account and more than 300 matching Page followers. It does not explicitly name alternatives or say when not to use it, so it stops short of a 5.

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