Create Theme

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

Adds value beyond annotations by requiring getThemeSchema, indicating the open-world nature and the need for schema knowledge. Annotations already state destructiveHint=false and openWorldHint=true, so this is a good supplement.

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 sentences, no wasted words. The first states purpose, the second gives critical usage guidance. Front-loaded and efficient.

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?

Covers purpose and a key prerequisite, but does not explain the return value or potential error states (e.g., if theme already exists). For a tool with no output schema, this missing context is a gap.

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 both parameters (realm enum, themeData object). The description adds that themeData must include a 'name' property, which is not in the schema but is critical for usage.

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?

Clearly states 'Create a new theme for a realm', specifying verb, resource, and scope. The prerequisite instruction distinguishes it from sibling tools like updateTheme.

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?

Explicitly instructs to call getThemeSchema first, providing clear context for use. Does not explicitly exclude alternatives, but the context is strong.

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