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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful operational context—app-only, backend-managed feature flags/counters/timeouts, and no paid API call from the browser—but remains vague about permissions, rate limits, or per-service behavior.

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 short and front-loads the domain, but the second sentence ('The backend retains feature flags, monthly provider counters and timeouts') is implementation detail that does not clearly help an agent invoke the tool.

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?

With no output schema, a nested payload object, and zero schema description coverage, the description should explain how to construct payloads per service. It does not, leaving the agent unable to call the tool correctly beyond guessing payload structure.

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%, and the payload is a nested object with no documented shape. The description hints at three of the four enum services (autocomplete/details/link preview) but says nothing about payload fields or how each service expects them.

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 identifies the domain as Places search/details and link previews, which aligns with the service enum. However, it never states a clear verb or the overall purpose of widget_lookup, and does not differentiate it from siblings like add_place or vote_place.

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 add_place, vote_place, or other place-related siblings. The description also gives no indication of how to choose among the four service values.

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