Create group

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

The description merely restates the action implied by the name and annotations (readOnlyHint=false indicates a write operation). It does not disclose side effects, permissions, naming constraints, or what happens if a group with the same name exists. Since annotations already carry the safety profile, the description adds no extra behavioral context.

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, clear sentence that directly states the action and resource with no wasted words. It is front-loaded with the verb, making it immediately 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?

For a simple one-parameter create tool with annotations and full schema coverage, the description is minimally adequate but lacks details about expected return values (no output schema) and any constraints on group names. It does not mention whether the group is created empty or if it can be immediately populated via sibling 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?

The schema already provides 100% coverage for the only parameter 'name' with the description 'The group name.' The tool description does not add any additional meaning or clarification for how the parameter should be used, so it stays at the baseline for full schema coverage.

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 'Create a new athlete group' uses a specific verb ('create') and resource ('athlete group'), clearly distinguishing it from other group management tools like tp_rename_group or tp_list_groups. It adds the qualifier 'athlete' to differentiate from other create tools (e.g., tp_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?

The description offers no guidance on when to use this tool versus alternatives such as tp_add_athletes_to_group or tp_rename_group. It does not mention any prerequisites, follow-up actions, or contexts where this tool is the appropriate choice.

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