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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behaviour, so the safety profile is covered. The description adds genuine context beyond that: the exact field set returned and the meaning of `needsReview` ('read from the website and not yet confirmed, so not offered'), which changes how an agent should treat those items. It could still note ordering or absence of pagination, hence not a 5.

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?

Front-loaded with purpose and sibling differentiation, then the field list, then the editing alternatives — a sensible order with no filler. The field enumeration is dense but each item carries information an agent needs to pick values.

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?

There is no output schema, and the description compensates by enumerating the returned fields and explaining the ambiguous one, so an agent knows what to expect. Only minor gaps remain (result ordering, whether the list can be empty or paginated) for an otherwise simple one-param read tool.

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% and the single optional `workspaceId` param is fully documented in the schema, including the default-scope behaviour. The description adds nothing about the parameter, so the baseline 3 applies.

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 and resource ('List the products and services the Ignix assistant can offer customers in chats') and immediately distinguishes itself from the closest sibling: 'This is the chatbot catalogue, not the link-in-bio store (list_store_products).' An agent can select it 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?

Gives explicit when-to-use guidance ('Quote prices from here rather than inventing them') and routes mutation intent to the correct alternatives (create/update/delete_catalog_item, confirm_catalog_items). It also names the sibling it is not, so the selection decision is fully specified.

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