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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: 'Looking is free' and results include full inputSchema, tier, price, and provenance notes. This gives agents a clear expectation of what the search returns.

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 somewhat long, but every sentence earns its place: use conditions, ordering vs locus_execute, result contents, exclusions, and an optional install command. It is front-loaded with the most important routing guidance.

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 catalog search tool with no output schema, the description is quite complete: it explains when to search, what the results contain, what it is not for, and how it relates to locus_execute. It lacks concrete examples or pagination details, but those are not critical for correct 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 100%, so the input schema already documents all four optional parameters. The description does not add parameter-level semantics beyond the catalog-search context, so the baseline of 3 is appropriate.

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 clearly states a specific action and resource: search the Locus tool catalog when you need official public records or local-government context for a US address/place and do not know the tool name. It also distinguishes itself from sibling locus_execute by saying to search before executing.

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 gives an explicit when-to-use rule with conditions, and it names the alternative behavior: search before locus_execute and before paying for a generic scrape. It also states exclusions such as 'Do not use this for LinkedIn, web scrape, or generic fetch,' so an agent has clear decision boundaries.

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