Litany

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

No annotations are provided, so the description carries the full behavioral burden. It mentions 'random wisdom,' hinting at nondeterminism, but does not disclose side effects, return behavior, permissions, or whether the ritual changes any state.

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 compact and front-loaded, first stating the ritual action and then listing its components. The flavor terms are colorful but slightly reduce operational precision rather than bloating the text.

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 no annotations, the description should explain what recitation returns and how each action behaves. It does not cover return values, action mapping, or side effects, leaving the agent with an incomplete picture despite some parameter descriptions in the schema.

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 schema covers 67% of parameters, but the required 'action' parameter has no schema description and the description does not map the five action values to concrete behavior. Terms like 'Inner Litany' and 'Sevenfold Rite' loosely echo schema concepts but do not clarify how 'recite', 'section', 'rite', 'invoke', and 'sevenfold' differ.

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 states a specific verb and resource: reciting sacred texts from the Codex Martianus before beginning work. However, the operational purpose is vague because 'sacred texts' and 'Inner Litany' are in-world terms rather than concrete actions, and it does not distinguish the tool from siblings like mcp_m7_warmup or mcp_m7_init_project.

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?

It gives a clear timing cue: use 'before beginning work.' But it does not say when not to use it, how it differs from adjacent preparation tools, or which action to choose for a given situation.

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