scaffold_dotnet_project

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

No annotations are provided, so the description bears the full burden of disclosing effects. It only says the tool 'generates' a project; it does not say whether files are written locally, whether existing directories are overwritten, whether the dotnet CLI is required, what the api_key is for, or what the tool returns.

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 with the core action front-loaded and no wasted words. It is appropriately concise, though the brevity pushes important semantics into 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?

Given no output schema and no annotations, the one-line description is insufficient for an agent to call this tool correctly. It lacks information about what files and structure are actually created, how the api_key is used, what templates map to, and how this tool differs from sibling .NET scaffolding tools.

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 all four parameters (project_name, template, dotnet_version, api_key) are already documented in the input schema. The description adds no specific parameter meaning beyond the generic 'folder structure and configuration,' so it stays at the baseline.

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 states a specific action ('Generate') and a concrete resource ('a .NET project'), and hints at what is included ('folder structure and configuration'). However, it does not differentiate this tool from adjacent siblings like generate_dotnet_solution or generate_dotnet_config, which could plausibly overlap.

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 guidance on when to use this tool versus alternatives. With many sibling scaffolding tools (scaffold_go_project, scaffold_spring_boot, generate_dotnet_solution), the absence of any condition or exclusion leaves the agent guessing.

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