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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read, open-web nature is known. The description adds 'public' and 'detailed' context but says nothing about auth needs, rate limits, or retrieval behavior. With annotations carrying the safety profile, this is a moderate contribution.

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?

Two tightly written sentences, front-loaded with the core action and followed by the routing guidance. Every clause earns its place with no 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?

For a single-parameter lookup with an output schema and existing annotations, the description supplies enough context to call it correctly. Return details are rightly delegated to the output schema, though a note on what 'detailed' encompasses is absent.

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 coverage is 100% and the single 'id' parameter is already documented in the schema. The phrase 'by product `id`' merely restates the schema without adding format or acquisition guidance beyond what the routing sentence implies.

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?

States a specific verb (fetch), resource (LinkedIn product), and scope (detailed public information by id). It explicitly names the sibling tools it is not, so an agent can distinguish it from linkedin_products_search and linkedin_product_categories without opening any schema.

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?

Names the two alternatives (linkedin_products_search to find products, linkedin_product_categories to browse categories) and the condition that selects each. This is an explicit when-to-use routing statement, leaving nothing to inference.

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