tpt_get_product

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the read-only nature is disclosed, but the description's 'Validate files' behavior is left unexplained. It also does not mention what happens on validation failure or what the read operation returns.

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 to the point, but the front-loaded 'Validate files' clause is tangential and not clearly related to the tool's primary function of reading product metadata. It is concise but not optimally structured.

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?

With no output schema and only a vague resource description, the tool lacks essential context about return values, error behavior, and how 'prepared product metadata' differs from other product-related tools. The description is too thin to fully support correct invocation.

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 only parameter 'id' has no description in the schema, and the tool description does not explain what kind of identifier it is. The pattern ^[a-z0-9-]+$ implies a formatted ID, but the meaning of that ID is entirely unspecified.

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 names a verb and resource—'read prepared product metadata'—but the phrase 'Validate files' is confusing and not clearly tied to the tool name or its siblings. It does not sufficiently distinguish this tool from tpt_product_status or tpt_list_products.

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 no guidance on when to use this tool, what prerequisites exist, or when to prefer it over sibling tools. The word 'prepared' hints at a workflow, but no explicit usage direction is provided.

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