Productboard MCP Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it returns details (not just summaries), is paginated, and has a fixed page limit of 100. However, it doesn't mention other important behaviors like rate limits, authentication requirements, error handling, or what 'detail' includes (e.g., fields returned).

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 sized with two sentences that each add value: the first states the purpose, the second adds critical behavioral context (pagination and limit). It's front-loaded with the core purpose. No wasted words, though it could be slightly more structured.

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 no annotations and no output schema, the description is incomplete. It covers the purpose and pagination behavior but misses parameter documentation, return value details, error conditions, and usage context relative to siblings. For a list tool with pagination, this leaves significant gaps for an AI agent.

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 0%, so the description must compensate. It doesn't mention the 'page' parameter at all, leaving it undocumented. However, since there's only one parameter and it's optional with a default, the impact is moderate. The description implies pagination but doesn't explain how the 'page' parameter interacts with it.

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 ('Returns') and resource ('detail of all products'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_product_detail' which presumably returns a single product's details versus all products.

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 like 'get_product_detail' or other list tools (e.g., 'get_components', 'get_features'). The description mentions pagination but doesn't explain when to use paginated vs. non-paginated alternatives if they exist.

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