Create a TaScan project as a top-level container for events, specifying a required name and optional location.
Create a new TaScan project (top-level container for events)
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Project name | |
| location | No | Project location / venue |
Changes observed during successful MCP inspections.
v3.12.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a non-read-only, non-destructive, non-idempotent operation. Description adds no additional behavioral context such as permissions, uniqueness constraints, or return behavior. It merely restates the create action.
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 concise sentence, front-loaded with the action and resource; no unnecessary words.
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 simple create operation with complete schema and annotations, the description provides enough context by explaining the project is a top-level container for events. It does not mention return values, but the absence of an output schema lowers the requirement.
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 provides 100% coverage with descriptions for 'name' and 'location'. Tool description adds no parameter detail 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?
Description uses specific verb 'Create' with resource 'TaScan project' and clarifies its role as 'top-level container for events', distinguishing it from sibling tools like tascan_create_event.
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?
Description does not explicitly state when to use this tool over siblings; it only implies usage via the project concept. No alternative tools or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.