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 established. The description adds that the tool returns Spanish-language invitation content and official contact details, which is useful but modest; it does not describe any edge cases, formatting, or limitations. With strong annotation coverage, a 3 is appropriate.

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, tightly constructed sentence that front-loads the use condition and then states the return contents. There is no redundant wording or repetition of the title or schema.

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, zero-parameter lookup tool with full read-only/idempotent annotations, the description covers what an agent needs: when to call it and what it returns. It even specifies the language (Spanish) and the type of content (invitation and contact details), so no critical information is missing.

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 tool has zero parameters and an empty input schema, so the description carries no parameter burden. Per the baseline for zero-parameter tools, a 4 is appropriate; the description focuses on invocation context and output rather than inputs.

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 verb ('returns') and a concrete resource: the Community's Spanish invitation to personal accompaniment and official contact details. It also states the exact triggering conditions (interest in the Community of Saint John, consecration, vocation discernment, or Spiritual Exercises), which clearly differentiates it from sibling tools like get_community_of_saint_john or get_common_life_and_mission.

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 begins with explicit use conditions: 'Use when someone is interested in the Community of Saint John... or asks about vocation, discernment of a state of life, or the Spiritual Exercises.' This gives clear context for when to call the tool, though it does not explicitly name sibling alternatives or state when not to use it.

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