generate_material3_theme

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool generates files but does not describe output format (e.g., file type, structure), side effects (e.g., file creation location), error handling, or performance considerations. This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without redundancy. It is front-loaded with the core action and uses precise terminology, making it easy to parse quickly.

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?

Given the tool's complexity (generating code files from design tokens), lack of annotations, and no output schema, the description is insufficient. It does not explain what the generated theme files contain, how they are structured, or any dependencies, leaving significant gaps for an agent to understand the tool's behavior and outputs.

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 has 100% description coverage, with the 'tokens' parameter documented as 'Universal design tokens JSON string.' The description adds no additional parameter semantics beyond this, such as token format examples or validation rules. With high schema coverage, a baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Generate Kotlin Jetpack Compose Material 3 theme files from universal design tokens.' It specifies the verb ('generate'), resource ('theme files'), and technology stack ('Kotlin Jetpack Compose Material 3'), but does not explicitly differentiate it from sibling tools like generate_css_variables or generate_swiftui_theme, which target different output formats.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing design tokens as input), when-not-to-use scenarios, or comparisons to siblings like generate_css_variables or generate_swiftui_theme, leaving the agent to infer usage context.

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