missive_create_teams

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

Annotations already declare destructiveHint=false. Description adds token requirement but doesn't disclose other behavioral traits (e.g., what happens on duplicate team names, limits on number of teams).

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, first sentence states purpose, second adds prerequisite and high-level body shape. 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?

Given many optional nested parameters and no output schema, description does not cover important details like defaults, validation rules, or response format. Adequate but not complete for a complex tool.

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?

Description adds meaning beyond schema by clarifying that 'organization' falls back to MISSIVE_DEFAULT_ORGANIZATION and that 'name' is required. Schema coverage is high but nested properties lack descriptions; this guidance aids agent usage.

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 states 'Creates one or more teams in an organization' with a specific verb and resource. It clearly distinguishes from other 'create' tools like create_contacts or create_draft.

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?

Mentions prerequisite that API token must belong to admin/owner, and hints at when to use (creating teams). Does not explicitly state when not to use or compare to alternatives.

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