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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds that responses are source-based and limited, which is useful behavioral context, but it remains vague about what sources are used and what 'limited' means in practice.

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 short, but it merely restates the title and contributes little information. This is under-specification rather than deliberate conciseness; a one-sentence caveat does not earn its place as a functional description.

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?

Although the tool is simple (one parameter, no output schema) and annotations cover safety, the description leaves out essential usage context: what kind of query is accepted, what the response looks like, and how this tool relates to the sibling tools. An agent cannot reliably decide to call it based on this description.

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 compensate by explaining the 'query' parameter, expected input format, or how queries are interpreted. The schema only provides type and length constraints, so the agent has no semantic guidance beyond the parameter name.

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?

No guidance is provided on when to use this tool versus its siblings. The phrase 'no free AI consulting' implies a limitation, but it does not state when an agent should choose saxsoc-geo-ask over saxsoc-geo-search, saxsoc-geo-compare, or saxsoc-geo-next-step.

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