product_get_expertise

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

The description goes well beyond the readOnlyHint annotation by explaining confidence levels, how observed/unknown entries must be phrased, and that the tool also lists what the user does not have. It also clarifies the server is read-only and cannot perform Reddit actions.

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 first paragraph is front-loaded and information-dense, but later paragraphs include generic policy guidance about Reddit participation and product promotion that is not specific to this tool. Some sentences repeat what annotations already convey, so not every sentence earns its place.

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?

The output schema covers return structure, and the description thoroughly explains the meaning and usage of the returned expertise entries. The main completeness gap is the absence of parameter semantics and the lack of explicit differentiation from sibling tools.

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%, and the description never mentions `tags` or `about` or explains how they shape the results. The parameter names are only weakly suggestive, so an agent has little guidance on what values to supply.

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 identifies the tool as exposing the user's first-hand expertise and positions it as the primary source for helping people. It distinguishes itself from product-marketing capabilities, though it never states an explicit action verb like 'retrieves' or 'returns'.

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 gives strong usage context: this is the primary source for helping people and contains no product marketing. It does not explicitly name sibling tools or state when not to use it, so it stops short of full alternative routing.

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