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

No annotations provided, so description carries full burden. It discloses authentication requirement and return format. It is clearly a mutating operation, but does not mention idempotency or if it overwrites/upserts.

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, front-loaded with purpose. Every sentence adds value: first defines action, second specifies parameter sources and return format. No fluff.

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?

Covers purpose, parameter sources, return format, and authentication. With no output schema in structured form, the description provides it informally. Could clarify what 'name' refers to (likely list name). Overall sufficient for action execution.

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 has 0% description coverage. Description adds significant context: explains origin of vertical and listing_id, and constraint on member_email. This compensates well for missing schema descriptions.

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 verb 'save' and resource 'listing to signed-in member's list'. Distinguishes from sibling 'unsave_place' and search tools via context about parameter sources.

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?

Explicitly states member_email must be authenticated, and vertical+listing_id come from get_/search_ tools. Implicitly guides when to use (after obtaining listing info) and prerequisite authentication. Could explicitly mention not to use if user is not signed in.

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