product_manager_get_metrics

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

No annotations are provided. The description does not disclose what the tool returns upon invocation (e.g., whether it provides detailed explanations, examples, or just a list). Behavioral traits are absent.

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 short and front-loaded with 'Product metrics.' It concisely lists frameworks in one sentence, avoiding redundancy.

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 output schema or annotations, the description is the sole source of context but fails to explain what happens when the tool is called. It does not clarify if it returns a guide, a summary, or interactive content, leaving the agent underinformed.

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?

With zero parameters, baseline is 4. The description adds value by listing the metric frameworks covered, giving semantic context beyond the empty schema.

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 lists metric frameworks but lacks a specific verb-resource structure. It vaguely suggests 'define what success is measured by' without clearly stating the tool's output (e.g., definitions, explanations). It is not a tautology but remains imprecise.

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 on when to use this tool versus sibling product management tools (e.g., product_manager_get_jtbd, product_manager_get_four_risks). The description does not differentiate usage contexts or mention alternatives.

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