product_page_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety and repeatability profile is fully covered. The description adds no behavioral context beyond the word 'Read', and does not describe side effects, permissions, or result characteristics beyond what the annotations and output schema provide.

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?

A single front-loaded sentence with no wasted words. It communicates the core operation and scope immediately.

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?

This is a simple getter with a fully documented input schema, rich annotations, and an output schema. The description does not need to explain return values or behavior in more depth, though it could note the context of profile and ad account scoping.

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 100%, so the schema already documents profile, adAccountId, and productPageId. The description's mention of 'Default or Custom' adds slight semantic color to productPageId but largely repeats what the schema states.

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 states a specific verb (Read) and resource (Default or Custom Product Page) scoped by ID, which clearly identifies a single-item retrieval operation. It is distinguishable from sibling listing tools like product_pages_query and product_page_locales, though it does not explicitly name them.

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 phrase 'by ID' implies this is the tool for fetching one known product page, while product_pages_query would be used for discovery. However, the description provides no explicit when-to-use guidance or named alternatives, leaving the agent to infer the distinction.

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