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

The annotations are minimal (only title), so the description carries the transparency burden. It clearly states 'Read' behavior, explains that spending limits are not here, and declares 'Auth required'. It does not detail error conditions or rate limiting, but the scope is well-defined.

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 front-loaded with the core read purpose, then provides actionable guidelines and transparency notes. It is dense but efficient, with each clause adding value. Minor redundancy in the spending limit note, but overall well-structured.

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's complexity (nested object, dual read/update behavior) and no output schema, the description covers the read behavior, update behavior via set_preferences, and distinguishes from spend policy. Could be more complete by hinting at error handling for invalid keys, but it's sufficient for an agent to use 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?

Since schema description coverage is 100% and there is only one parameter (set_preferences), the description adds value by explaining the behavior of omitting set_preferences (read mode) vs. providing it (merge-update, allowlisted keys only, null clears). It also explains the context for each sub-field (e.g., 'Accessorial slugs to apply by default') beyond the schema alone.

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 the tool reads a shipper profile including derived server-side data and owner-set preferences, and distinguishes itself from the related set_preferences action and the separate spend policy tool. The verb 'Read' and the structure of the description make the tool's purpose unambiguous.

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 description explicitly tells the agent to 'READ THIS BEFORE asking the user questions it already answers' and provides concrete pre-fill examples (usual lane, standard dims, liftgate). It also clearly explains when to use set_preferences to update, and distinguishes the profile from spend policy, which is read-only via another tool.

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