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

Annotations already mark this as read-only and non-destructive, and the description adds useful behavior beyond that: every entry includes definition, provenance class, century, and sources, and the API deliberately prevents conflating rabbinic and Christian/modern traditions. It does not discuss edge cases or limitations, but for a static catalogue list the core behavior is disclosed.

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 few sentences long and front-loads the main action and scope before adding context about provenance and intended audience. It is slightly dense, but no sentence is wasted.

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?

With no output schema and a simple list endpoint, the description carries the burden of describing the return payload. It specifies the categories, the per-entry fields, and the semantic guarantee about provenance, which is enough for an agent to select and invoke the tool correctly.

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?

Both parameters (lang, compact) are fully described in the schema, so the description does not need to repeat them. The description itself adds no parameter-level guidance, which meets the baseline for 100% schema coverage.

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?

Starts with a strong verb and concrete object ('Return the full catalogue of gematria methods') and enumerates the exact scope: eleven rabbinic ciphers, two substitution transformations, and three Latin alphabet ciphers. This makes the tool clearly distinct from sibling endpoints focused on names, letters, daily readings, and birth profiles.

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 names the intended use case: calculators that need to show which method produced a number and where the method comes from. It does not explicitly contrast with sibling tools or say when not to use it, but the resource type itself differentiates it clearly.

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