Find a location ID

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them by naming the account-type and permission prerequisites for each input mode. It does not say what is returned on success or what happens when the page cannot be resolved, which matters for an open-world lookup.

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 key fact is front-loaded and the total length is small. The nested parenthetical in the second sentence is dense and slightly harder to parse than a two-bullet structure would be, but nothing is wasted.

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 three-optional-parameter lookup with no output schema, the description covers the prerequisite conditions well. It leaves implied rather than stated whether 'page' and 'query' are mutually exclusive and what the successful result actually contains, which is the main remaining gap.

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 all three parameters are already documented, making 3 the baseline. The description does add meaning the schema lacks, namely that 'query' is gated behind Page Public Metadata Access and that 'page' depends on a Facebook Login account, which isn't visible from the schema alone.

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 first sentence states the specific domain fact ('Instagram location tags use the Facebook Page ID of a place') and the second states the action: pass a page or a query to resolve it. That is a concrete verb+resource and it is unlike any sibling in the list, which are all publishing, commenting, or analytics tools.

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?

It clearly routes the agent between the two input modes: 'page' works for Facebook Login accounts, while 'query' requires Meta's Page Public Metadata Access, 'which most apps don't have.' It even supplies a fallback for apps lacking that permission (look the place up on facebook.com and pass its Page URL). It stops short of tying the call to a downstream use such as tagging in publish_photo.

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