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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds content-scope information (what fields each listed mudra exposes) which is useful, but says nothing about result size, ordering, or whether the catalog is static.

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?

A single sentence with the verb and resource front-loaded and no filler. Every clause (compositions, preconditions, execution skeletons) conveys what the returned records contain.

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 parameters, no output schema, and safety covered by annotations, the description's main job is to characterize the result set, which it does by naming the three things each entry carries. Only the scale and ordering of the catalog are left unstated, a minor omission for a no-argument listing tool.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description does implicitly confirm the no-argument 'list all' behavior by saying 'all recognized' rather than implying filtering options.

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 (List) and a specific resource (canonical compound Taoist Mudras), and even enumerates what each entry carries: compositions, preconditions, execution skeletons. It is clear what the tool does, but it never distinguishes itself from close siblings like sutra.canon or sutra.cast, so an agent cannot tell from the text alone which of these to pick.

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 says 'List all recognized' but gives no when-to-use condition, no prerequisites, and no mention of alternatives such as sutra.canon or sutra.compile. With several similarly named sutra.* siblings, the absence of routing guidance is a real gap.

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