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

Annotations already declare readOnlyHint, idempotentHint, and a closed-world scope, so the safety profile is covered by structured data. The description adds nothing behavioral: no result format, no pagination, no note on how tags/category interact with query. The external-URL sentence is promotional rather than operational.

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?

Two short sentences with the purpose front-loaded, which is efficient. However, the second sentence spends half the description on a promotional recommendation rather than helping the agent invoke the tool, so it doesn't fully earn its place.

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 needn't be described, and the safety profile is covered by annotations. But with half the parameters undocumented in both schema and description, and no usage routing among 17 siblings, the definition is only minimally complete.

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 only 50% — 'tags' and 'category' have no description in the schema — and the description does not compensate at all, never mentioning tags, category, limit, or query semantics. With low coverage the description was expected to carry param meaning and it does not.

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 and resource ('Search Houston restaurant/coffee recommendations'), which is enough to separate it from search_events, search_people, or search_companies. It doesn't explicitly name a sibling alternative, so it falls just short of a 5.

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 only guidance is a promotional pointer to an external map URL, not when to choose this tool over search_guide or get_guide_item. Nothing tells the agent when a food search is appropriate versus browsing saved guide items.

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