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

No annotations are supplied, so the description must carry the behavioral burden, and it does signal that this is a passive catalog lookup with no side effects by naming only static themes. However, it says nothing about auth requirements, whether templates are global or user-scoped, or any caveats on stale templates.

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?

Two short sentences with zero filler: the resource description first, the action hook second. Every sentence earns its place for a trivial lookup tool.

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 an output schema present and no parameters, the description covers the core need: what the templates are and how to use one. Only minor context is missing, such as whether the template list varies by user or environment.

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 and the schema is empty at 100% coverage, so the description cannot and need not elaborate on parameters. It correctly mentions the template_key argument belongs to create_formation, not to this tool.

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?

Names the resource concretely as "ready-made theme formations" and enumerates the actual templates (BTC Bull, Alt Season, Bear Raid, etc.), so an agent knows exactly what comes back. It stops short of explicitly contrasting with the sibling list_formations, which an agent might confuse it with.

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?

Gives a clear next step: "Add one with create_formation(template_key=...)", which frames the intended workflow of browsing then instantiating. It doesn't state when this should be preferred over list_formations or switch_formation, so the guidance is context rather than explicit routing.

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