manage_team

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

No annotations are provided, so the description carries full burden. 'Manage' implies mutation operations (inviting, removing, updating), but the description doesn't disclose critical behavioral traits: required permissions, whether changes are reversible, rate limits, or what happens on success/failure. For a tool with multiple mutation actions and no annotations, this is a significant gap in 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?

The description is extremely concise—a single phrase with zero wasted words. It's front-loaded with the core purpose, though this brevity comes at the cost of detail. Every word earns its place by conveying the essential scope, making it structurally efficient despite informational gaps.

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 the tool's complexity (multiple mutation actions via 'action' enum) and lack of both annotations and output schema, the description is incomplete. It doesn't address behavioral risks, output expectations, or error conditions. For a tool that can invite, remove, or update permissions—potentially destructive operations—the description should provide more context to guide safe usage.

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%, so the schema already documents all three parameters with descriptions and enums. The description adds no additional meaning beyond the schema—it doesn't explain parameter relationships (e.g., 'email' is only needed for certain 'action' values) or provide context like format requirements. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Manage team members and permissions' states the general purpose (verb+resource) but is vague about specific actions. It distinguishes from most siblings like 'create_form' or 'get_submissions' but doesn't clearly differentiate from 'manage_workspace' which might have overlapping functionality. The description lacks specificity about what 'manage' entails.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or exclusions. While the input schema's 'action' enum implies different use cases, the description itself offers no usage instructions, leaving the agent to infer from parameters alone.

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