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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — the server marks it read-only so it 'runs straight away' (no approval gate) — but says nothing about return shape, error handling, or how the nested arguments object is consumed.

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?

Only two short sentences and the resource is front-loaded, so it is compact. But the phrasing is fragmentary and the 'Through Royally' clause is opaque vendor jargon that costs a sentence without earning its place.

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?

This is a generic operation-dispatch tool with a nested free-form arguments object and no output schema, which is a complex surface. The 'omit operation to list them' hint is the saving grace, but the description still leaves an agent unsure what operations exist and what the arguments payload should look like.

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 coverage is 100%, so the schema already documents site_id, operation, and arguments, and the description's 'call with no operation' note largely repeats the operation field's own text. It adds no detail about what keys the nested 'arguments' object expects for any operation, which is the one place semantics were actually needed.

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 is essentially a restatement of the tool name: 'Active Theme, read operations' mirrors 'theme-read'. It names the resource (active theme) and the mode (read) but supplies no verb describing what is actually retrieved, and it does nothing to distinguish it from siblings like emcp-tools-list-themes, emcp-tools-get-settings, or emcp-tools-search-themes.

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?

'Call with no operation to list them' gives a concrete discovery workflow, which is real usage guidance. However, it never says when to pick this tool over the many theme/settings siblings, nor any prerequisites, so the guidance is partial and inferred rather than explicit.

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