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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: feature flags, monthly provider counters and timeouts live in the backend, implying quota/counter behavior worth knowing. It stops short of describing pagination, error behavior, or what the counters mean for the caller.

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?

Three short sentences, front-loaded with the capability statement. Every sentence carries some information, though the 'paid API from the browser' line is more about implementation posture than tool selection.

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 tool with a required, undocumented nested payload, four service modes and no output schema, the description is inadequate. It omits the per-service payload contract entirely, which is the single most important thing an agent needs to invoke this correctly.

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 an untyped nested object with no field documentation anywhere. The description's mention of search/details/link previews loosely maps to the service enum, but says nothing about the required 'payload' shape for each service, leaving the caller to guess.

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 concrete capabilities (Places search/details and link previews) that map onto the four enum service values, so the agent knows what the tool fetches. However, it never reconciles this with the tool's own name 'widget_lookup' and offers no explicit differentiation from siblings like add_place or find_plan_mentions.

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 statement of when to use this tool versus add_place, vote_place, or any other sibling. The only constraint offered ('Never calls a paid API from the browser') is an implementation note about the backend, not guidance on when an agent should select this tool.

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