sprout-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a list operation (implying read-only) but doesn't mention pagination, rate limits, authentication requirements, sorting, filtering capabilities, or what happens when no customer_id is provided. The default behavior is mentioned but not fully explained.

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 appropriately concise with two sentences that each serve a clear purpose. The first states the tool's function, and the second explains the parameter. There's no unnecessary information, though the structure could be slightly improved by front-loading the most critical information more explicitly.

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 that this is a simple list operation with one optional parameter and an output schema exists, the description is minimally adequate. However, with no annotations and incomplete behavioral disclosure, there are gaps in understanding authentication, pagination, and error handling that would help an agent use this tool effectively.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explains that 'customer_id' is a 'Sprout customer ID' and mentions the default behavior of using the SPROUT_CUSTOMER_ID environment variable. This provides crucial context that the schema alone doesn't convey.

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 the verb ('List') and resource ('all teams for a customer'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'list_customers', 'list_groups', or 'list_users', which all follow similar list patterns for different resources.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, constraints, or relationships with sibling tools like 'list_customers' (which might provide the customer_id needed here) or 'list_groups' (which might list a different type of organizational unit).

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