cpp

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

The description adds behavior beyond annotations: it states that no network access or compilation occurs, and enumerates the exact files generated. It also says it aligns with the official example, giving the agent confidence about the output. Annotations already mark idempotent hint, so no contradiction.

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, information-dense sentence with a leading summary and parenthetical detail. Every element (files, constraints, alignment) is relevant and there is no fluff.

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 scaffolding tool with fully annotated schema and idempotent hint, the description provides the essential output details and constraints. It does not need to describe return values since there is no output schema, and the file list gives the agent a clear expectation of side effects.

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 descriptions cover 100% of the parameters, including enums and defaults. The description adds no extra parameter-level detail beyond stating that scaffold_gdextension operates in project_path, which is already clear from the schema. Baseline 3 applies.

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 it generates a GDExtension C++ project skeleton, listing specific deliverables (src/class.cpp/.h, register_types, SConstruct, .gdextension, .gitignore, README). It uses a specific verb '生成' and resource, and the scope (Godot C++ GDExtension) differentiates it from sibling tools like script or project.

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?

It provides clear context: used for scaffolding a godot-cpp GDExtension project under project_path, and notably states it does not network or compile, which prevents misuse. However, it does not explicitly mention alternative tools or when not to use it, though the sibling list implies no close alternative.

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