product_manager_get_prioritization

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to specify the output format (e.g., text descriptions, a list) or any side effects. The tool likely returns static content, but this is not stated. The description only lists frameworks and usage, omitting critical behavioral details.

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: two sentences that front-load the key content (list of frameworks) and conclude with a clear usage statement. Every word serves a purpose, with no redundancy or filler.

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?

While the description covers the tool's purpose and included frameworks, it lacks details about the output (e.g., format, structure). Since there is no output schema, the description should compensate by specifying what the agent can expect as a response. This gap reduces completeness for a tool with no parameters.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameter behavior, and it appropriately avoids misleading statements about inputs.

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 clearly states the tool provides prioritization frameworks (MoSCoW, Kano, ICE, WSJF, opportunity scoring) and its purpose: to decide what to build and in what order. It distinguishes from sibling tools like product_manager_score_rice (specific RICE scoring) by focusing on frameworks beyond RICE. The verb 'get' implies retrieving information, which aligns with the context.

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 includes a usage directive: 'Use to decide what to build and in what order.' This provides clear context for when to invoke the tool. However, it does not mention when not to use it or suggest alternatives (e.g., product_manager_score_rice for RICE scoring, product_manager_get_roadmapping for planning), leaving some ambiguity for the agent.

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