generate-component-scaffold

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

With no annotations provided, the description carries the full burden of behavior disclosure. It mentions generation and returns production-ready code, but omits key behaviors such as the listScaffolds mode (returning a list instead of code), filtering by library/category, and the effect of customizations on template variables. It also doesn't state whether it has side effects or dependencies, leaving significant behavioral aspects unclear.

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 sentence that is front-loaded with the verb 'Generates'. It is concise, includes relevant examples, and the phrase 'production-ready, type-safe code following best practices' conveys quality without excess. Every word contributes to the core message, and the length is appropriate for the tool's complexity.

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 tool has 8 optional parameters, including a list mode (listScaffolds), filtering, and a nested customizations object, yet the description omits these features entirely. Without an output schema, the description should explain return values, but it only vaguely states 'Returns production-ready, type-safe code.' The description is insufficient for a user to know how to list scaffolds, use filtering, or handle customizations, making it far from 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides. Each parameter has a clear description, including enums and defaults, so the description does not need to compensate. The minimal addition is the phrase 'like FlatList, navigation screens...' which hints at categories but doesn't clarify parameter usage beyond the schema.

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 function: it generates boilerplate code for specific React Native patterns (FlatList, navigation screens, forms, API calls). The verb 'Generates' plus the resource 'boilerplate code for common React Native patterns' distinguishes it from sibling documentation/search tools. The mention of 'production-ready, type-safe code' further clarifies the output quality.

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 like search-docs or get-best-practices. It doesn't mention the listScaffolds mode as an alternative usage, nor does it advise when to use filtering parameters. The only implicit hint is that it's for code generation, but no explicit when/when-not or alternative references are given.

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