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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description's added value is the authorization requirement and the membership constraint on teams, both of which are genuinely useful beyond the structured metadata. It stops short of noting failure modes such as duplicate team names or what happens on permission denial.

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?

Three short sentences with zero filler; the core action is front-loaded and each subsequent sentence adds a distinct constraint or routing hint.

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 two-parameter mutation with no output schema, the description covers purpose, permissions, membership constraint, and the logical next step. It doesn't say whether the response returns a team id needed by add_team_member, which would be the remaining gap.

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% and both required parameters are documented in the schema, including the note that org_id comes from list_organizations. The description adds no further parameter meaning, so the baseline 3 applies.

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 verb and resource ('Create a team inside an organization'), scoping it clearly apart from siblings like create_organization and add_team_member. An agent can tell immediately which tool creates a team versus which one adds people to it.

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?

It states the required permission ('Only an organization owner or admin can do this') and routes the agent to the follow-up tool ('Then add people with add_team_member'), plus the constraint that only org members can join. There is no explicit when-not-to-use, but the precondition and next-step routing are concrete.

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