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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds useful context with 'read from the house's pages at call time', implying live/fresh data, but says nothing about result volume, pagination, or coverage limits.

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 purpose is front-loaded and the example queries are valuable, but the parenthetical 'thousands of campuses, churches near campus, students, a path to follow Jesus' is promotional filler that dilutes the operative information. Overall readable but not tight.

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 need not be explained, and annotations carry the safety profile. With a single fully-documented required parameter, the description supplies everything an agent needs to call it, missing only sibling differentiation.

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% and the single parameter's schema already states 'A country, a US state, or a city.' The description merely restates this, adding no format hints (e.g., spelling, abbreviations, city disambiguation) beyond the schema.

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 names a specific resource — 'University Kingdom Network pages: Christian community at universities by country and region' — with a clear retrieval scope. It is distinguishable from generic siblings, though 'churches near campus' overlaps with find_churches_near and find_gatherings_near without acknowledging the difference.

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?

Usage is only implied: 'Pass a country, a US state or a city' plus example user questions ('Christian groups at universities in Japan') show the intended context. There is no explicit when-to-use guidance, no exclusions, and no named alternatives such as find_churches_near or church for the churches-near-campus case.

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