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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by explaining that profiles carry shipper/return addresses and carrier credentials, that CarrierInfo is read-only, and by disclosing two non-obvious behaviors (BillThirdParty=true suppresses rate quotes on UPS/FedEx; InheritedFromMaster=true borrows master credentials). That is real value beyond the annotations, though it says nothing about result volume or pagination.

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 the core action and filters, then moves to domain behavior; every sentence carries information and none is redundant. The trailing '[DEMO]' marker is slightly noisy but does not obscure the content.

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 an output schema present, return-shape explanation is not required, and the description still pre-empts confusion about the CarrierInfo array. Combined with full schema coverage and clear annotations, an agent has everything needed to call this correctly.

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 three filter parameters are already fully documented with types and meanings. The description only restates them by name without adding matching semantics (e.g., exact vs partial name matching, whether filters combine with AND). Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('List shipping profiles') plus the available filter dimensions, which is unambiguous. It doesn't explicitly name teapplix_manage_shipping_profile as the mutation counterpart, so the read/write split is only implied by the verb.

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 filter list hints at how to narrow results, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling teapplix_manage_shipping_profile that would be the alternative for creating or editing profiles. Usage is inferable but not stated.

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