get_data_product

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

The description only says 'Get details', implying a read operation, but does not disclose any behavioral traits such as error handling, permissions, or the ability to include deleted items (despite an 'include_deleted' parameter). With no annotations, the description carries the burden but fails to provide transparency.

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 a single sentence and front-loaded, but it is too brief to be fully informative. While concise, it sacrifices completeness and does not earn its place given the available space for more detail.

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 the tool has 3 parameters, no output schema, no annotations, and several sibling tools, the description is insufficient. It does not explain the parameters, differentiate from siblings, or describe the return value, making it incomplete for effective use.

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 0%, meaning the schema has no parameter descriptions. The description only hints at the 'data_product_id' parameter by mentioning 'by ID', but does not explain the 'fields' or 'include_deleted' parameters. This adds minimal value beyond the 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 clearly states it gets a specific data product by ID, using the verb 'Get' and resource 'data product'. However, it does not differentiate from the sibling tool 'get_data_product_by_name', which also retrieves a data product but by name.

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 is provided on when to use this tool versus alternatives like 'get_data_product_by_name'. There are no recommendations or exclusions, leaving the agent without context for tool selection.

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