create_team

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

Discloses owner auto-addition and production alternative. Without annotations, lacks details on side effects, error conditions, or required preconditions (e.g., wallet_address must be registered, which is only in schema). Moderate transparency.

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?

Two sentences with zero wasted words. Front-loaded with purpose, then key automatic behavior, then usage note. Highly concise.

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 tool with 3 parameters and no output schema, the description covers purpose, auto-add, and production alternative. Lacks return value info and error handling, but overall adequate given schema richness.

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 three parameters with descriptions. The tool description adds no new parameter information beyond what is in the schema, so baseline score of 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 clearly states 'Create a new agent team for multi-agent trust scoring' with a specific verb and resource. It also mentions the owner auto-add behavior, which distinguishes it from siblings like team_trust_check.

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 guidance to prefer the REST API for production, implying this tool is for non-production or simpler use. However, it does not directly compare to sibling tools or specify when to use this tool over them.

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