list_shipping_profiles

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

Discloses that include_addresses defaults to False to avoid exposing personal details. No annotations exist, so description carries burden. No mention of permissions, rate limits, or return behavior beyond the parameter.

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?

Two sentences: one for purpose, one for parameter. No extra verbiage. Front-loaded with core purpose. Every word earns its place.

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?

Lacks response format, pagination, error handling, or confirmation. With no output schema, description should explain what a 'shipping profile' contains. Adequate for its simplicity but incomplete for full agent self-sufficiency.

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% but the description fully explains the parameter: why it defaults to False, what it includes (full contact/address fields), and the rationale for defaulting. Adds significant meaning 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?

Clearly states the verb 'list' and resource 'saved local shipping profiles'. Distinguishes from sibling tools like save/delete_shipping_profile. No ambiguity.

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 on when to use this tool vs alternatives like save_shipping_profile or search tools. No when-not or prerequisite context. Implied usage is minimal.

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