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

The annotation readOnlyHint=true already signals the tool is safe to call without side effects. The description adds behavioral context by explaining that this is an introductory guide, not a data operation, and provides current catalog scope details. It does not contradict the annotations.

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 front-loaded with the most important guidance ('Call this first') and then supplies a compact learning path. The catalog detail is relevant and not redundant, and every sentence contributes useful context for invoking the tool correctly.

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 tool with one optional parameter and no output schema, the description gives enough guidance to know when and how to call it, what concepts it introduces, and what to do next. It does not specify the exact return format, but for a guide-style tool this is a minor gap.

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?

The only parameter, 'question', is fully documented in the schema as an optional natural-language question. The description itself does not elaborate on the parameter, but schema coverage is 100%, so the baseline score of 3 applies.

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 identifies the tool as a free starting guide and explicitly instructs the agent to 'Call this first' to learn the geometry/geography concepts. It also distinguishes this tool from siblings by placing it first in the learning sequence and pointing to get_tool_help for individual tool details.

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 description gives an explicit usage sequence: call this tool first, then read the live geometry catalog, then use get_tool_help for a specific tool. This makes when-to-use and the relationship to sibling tools unambiguous.

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