Create a new category group to organize budget categories. Use it to structure your budget and group related spending categories.
Create a new category group for organizing budget categories.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name for the new category group |
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=false, indicating this is a write operation, so the description doesn't need to state that. However, the description adds no further behavioral context, such as whether the group starts empty, requires permissions, or has side effects. It provides only the minimal verb and object, so it doesn't add value beyond the annotation.
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, concise sentence that front-loads the primary action and purpose. It contains no filler or redundant information, making it easy to parse quickly.
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 one parameter and no output schema, the description provides sufficient information for an agent to understand the tool's purpose. It could optionally mention that the new group starts empty or that categories can be added later, but this is not essential given the tool's simplicity. The description is adequate.
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?
The schema fully documents the single parameter 'name' with a description 'Name for the new category group' (100% coverage). The tool description repeats the purpose but adds no additional semantics, constraints, or examples. Given the high schema coverage, a baseline of 3 is appropriate; the description doesn't enhance parameter understanding.
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 the verb 'Create' and the resource 'category group', and explicitly mentions its purpose of organizing budget categories. This distinguishes it from siblings like create_category (which creates a category within a group) and update_category_group/delete_category_group. The intent is unambiguous.
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?
The description implies usage (when you need a new category group) but does not explicitly state when to use this vs. alternatives, nor does it mention any prerequisites or exclusions. It relies on the name and context to infer the appropriate use case. While it's straightforward, there's no direct guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.