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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations: returned guide content should be treated as source material, not as actionable instructions. This is genuinely useful for an AI agent deciding how to use the output.

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 a single compact sentence with no filler, and the key search action appears first. It is appropriately front-loaded. However, it duplicates the title verbatim rather than adding structured elaboration.

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 simple, read-only search tool with two basic parameters and no output schema, the description covers the core purpose and an important interpretation caveat. It does not mention result behavior, empty results, or how this relates to sibling tools, but the tool is simple enough that the description is minimally sufficient.

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 description does not explain either parameter (query or limit). Since the description must compensate for missing schema descriptions, this is a clear gap. The parameter names are self-explanatory, but no additional semantics or constraints are communicated.

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?

Tautological: description restates name/title.

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 about when to use this search tool versus siblings such as saxsoc-geo-ask, saxsoc-geo-compare, or saxsoc-geo-programs. The only contextual hint is about how to treat the results, not about when to invoke this tool instead of an alternative.

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