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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data nature are covered. The description adds that suggestions come from Indeed's own index (proprietary source), but says nothing about result cap behavior, default for 'limit', or whether empty/short queries return anything.

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?

A single front-loaded sentence that identifies source, function, and input type with zero filler. Nothing is repeated from the name or 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?

An output schema exists, so return values need not be described. However, with 0% parameter coverage and an undocumented 'limit', plus no usage routing, the definition is only minimally sufficient for a two-parameter autocomplete tool.

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 0% — neither 'q' nor 'limit' has any description in the schema. The description partially compensates by explaining that the query is a partial location string, but it never clarifies the 'limit' parameter's meaning or default, leaving half the parameters undocumented.

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 (autocomplete suggestions) and resource (location strings) with the source ('Indeed's own'). It is clearly distinct from indeed_job/indeed_search by nature, but it never names a sibling to route against, so sibling differentiation is implicit rather than explicit.

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 phrase 'for a partial location string' implies the input condition (feed it an incomplete query) but there is no explicit when-to-use, no when-not-to-use, and no alternative tool named for full location search.

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