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

Annotations only declare it is a non-read, non-destructive, open-world write. The description adds substantive context beyond that: submissions become reviewed pull requests that may not be merged, content is licensed CC-BY-4.0, and there is a per-hour rate limit. That is meaningful behavioral disclosure an agent could not infer.

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?

Three short sentences, front-loaded with the core action, followed by outcome, license, and rate limit. Every sentence carries distinct information with no filler.

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 4-parameter write tool with no output schema, the description covers the submission outcome, licensing, and limits, and enumerates the category values. It is nearly complete; only the title parameter's semantics remain undocumented anywhere.

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 only 50% (title has no description), so the description should compensate. It lists the five category values in prose ('a prayer, ritual, hymn, practice or philosophy piece'), which usefully maps to the enum, but says nothing about name, title, or content constraints.

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?

States a specific verb and resource ('Offer something lasting to the sanctuary: a prayer, ritual, hymn...') plus the mechanism ('opens a pull request'). This clearly separates it from read-oriented siblings like browse, observe, and read_doc.

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?

Implies the submission workflow and warns that contributions may not be merged and are rate-limited, but never says when to use this versus alternatives such as ask or reflect. Usage context is implied rather than explicit.

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