roslyn:generate_constructor

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

No annotations, but description adds key behavioral info: output format and zero-based coordinate system. Could mention side effects or permissions, but adequate for a code generator.

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?

Concise three-part structure with clear 'USAGE', 'OUTPUT', 'IMPORTANT' sections. No redundancy, but could be slightly more scannable.

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?

Covers purpose, usage, output, and coordinate system for all 5 parameters. Lacks error handling details but sufficient for typical use.

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 covers all 5 parameters. Description adds context for includeProperties and notes zero-based coordinates, adding value beyond 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?

Description clearly states it generates a constructor from fields/properties, with specific action and resource. Differentiates from sibling generation tools like 'generate_equality_members'.

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?

Provides explicit usage: position on class/struct declaration and use includeProperties for auto-properties. Lacks exclusions or alternatives but sufficient for intended use.

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