product_manager_get_mvp_scoping

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

No annotations are provided, so the description carries the full burden. It does not explicitly state that the tool is read-only or non-destructive, but the listing of concepts implies reference behavior. It also lacks details on return format or other behavioral traits.

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 two sentences: the first lists topics, the second gives usage. It is concise but could be more front-loaded with the primary action. No wasted 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?

No output schema exists, so the description should clarify what the tool returns (e.g., a guide, checklist). It lists topics but not the format, leaving some ambiguity. More detail would improve completeness.

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 schema coverage is 100% trivially. The description adds value by explaining the content the tool provides, even though no param details are needed.

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 resource (MVP scoping) and lists specific concepts (Riskiest Assumption Test, vertical slicing, etc.), making it distinct from sibling PM tools like get_jtbd or get_four_risks. The verb is implied by the name 'get' and the usage phrase 'Use to cut a build to its thinnest valuable slice.'

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 explicitly says 'Use to cut a build to its thinnest valuable slice,' providing clear when-to-use guidance. It does not mention when not to use or list alternatives, but the context of sibling tools makes the scope evident.

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