Nextjs Helpers Generate

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether files are written to disk, what happens if output_dir already contains files (overwrite/skip), what the generated files depend on, or what permissions/capabilities are required. For a code-generation write tool, this is a significant gap.

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?

One short sentence, front-loaded with the verb and resource, and every word earns its place. Its problem is under-specification rather than verbosity, which is penalized in the other dimensions.

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?

An output schema exists, so return values need not be described, but the description still omits critical context: the format of entity_types, the on-disk side effects of generation, and the relationship to the parallel gatsby_helpers_generate tool. For a file-generating tool with 0% schema coverage, this is not complete enough.

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 0% and neither of the two parameters is explained. The phrase 'Drupal entities' loosely gestures at entity_types but never states the expected format (machine names? bundle IDs? array syntax), and output_dir is not mentioned at all despite its default path semantics.

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?

States a specific verb and resource ('Generate Next.js helper functions') with a scoping phrase ('for Drupal entities'), which is enough for an agent to know the general output. It does not, however, distinguish itself from the very similar sibling gatsby_helpers_generate, so differentiation is left to the name alone.

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?

There is no when-to-use guidance whatsoever: no mention of prerequisites (a reachable Drupal JSON:API/GraphQL endpoint), no indication of when to prefer this over gatsby_helpers_generate, and no exclusions. The agent must infer usage entirely from the name.

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