manage_product

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

With no annotations provided, the description carries the full burden for behavioral disclosure. The action names (create/update/get/list) imply mutation or reads, but the description does not disclose side effects, permissions, reversibility, or response behavior. The mandatory-field notes are parameter semantics, not behavioral 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 compact and well-structured as an Args list. Each line communicates a distinct piece of information without redundancy. The 'Unified product operations' opener is slightly generic, but the overall length is appropriate for a multi-action tool with 12 parameters.

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 complexity of a CRUD tool with 12 parameters and no annotations, the description covers parameter usage well but omits broader context: it never states whether updates are partial or full, whether actions require special permissions, or how this tool relates to alternatives. An output schema exists, so return-value details are not required, but actionable guidance for tool selection and side-effect expectations is missing.

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%, so the description must compensate, and it does thoroughly. It explains every parameter's role, gives mandatory flags ('create — MANDATORY'), notes action-dependent requirements, distinguishes HTML vs plain-text description, and provides examples ('buy', 'lease'). This adds substantial meaning beyond the raw 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 states 'Unified product operations' and enumerates the supported actions ('create', 'update', 'get', 'list'), making it clear that this is a CRUD-style tool for products. It is distinct from the many sibling 'manage_*' tools because it names the product resource, but the term 'Unified' adds little specificity.

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 Args list gives concrete usage context: which parameters are required for which actions (e.g., product_id for get/update, name and asset_type_id mandatory for create, pagination for list). It does not explicitly mention when not to use this tool or name alternatives, but the action-specific requirements are clear and actionable.

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