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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by stating that it returns a complete public manifest (including tokens) and the theme's docs, implying no authentication for public themes. It doesn't mention error behavior or output format, but for a read-only fetch this is acceptable.

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?

The description is one sentence that front-loads the action and resource. Every word contributes: 'complete public manifest' sets scope, and the list of docs is explicit. No filler or redundant phrasing.

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 simple tool with one parameter, existing annotations, and no output schema, the description adequately conveys the tool's purpose and returned contents. It could be more explicit about the returned data structure or error cases, but given the low complexity, it is reasonably complete.

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 input schema covers the single 'slug' parameter with a description, so schema coverage is 100%. The description doesn't add any additional parameter-level details beyond what the schema already provides; it only refers to 'a theme' without elaborating on formatting or validation.

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 uses the specific verb 'Get' and identifies the resource as a theme's complete public manifest, including tokens, plus AGENTS.md and README.md. This clearly distinguishes it from siblings like download_theme (likely package download) and get_component (single component). The scope is precise.

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 doesn't explicitly state when to use this tool instead of alternatives, nor does it mention exclusions. The usage is implied by the description itself, but it does not reference sibling tools like search_themes or download_theme, so the agent must infer the appropriate context.

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