Validate Listing Text

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Validate' implies a non-mutating check and 'before updating' signals that it does not perform the update, but the description does not disclose what happens on invalid input or whether validation blocks the update. This is a moderate disclosure for a simple validation tool.

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 a single, front-loaded sentence with no filler or redundant wording. It fully states the tool's purpose in eight words, which is ideal for quick agent comprehension.

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?

The tool has only three optional parameters, all documented in the schema, and an output schema exists to describe return values. The description provides the essential purpose and timing context, though it could be slightly more explicit about being a prerequisite for update_listing and about validation failure behavior.

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%, with each parameter already describing its max length, so the description does not need to add per-parameter detail. The description's mention of 'text lengths' collectively matches the three text parameters, but it adds no information 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?

The description states a specific verb ('validate'), a specific resource ('store listing text lengths'), and the context ('before updating'). It clearly distinguishes itself from the sibling update_listing tool by indicating it is a validation step rather than the update operation itself.

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 phrase 'before updating' gives clear temporal context for when to use this tool, implying it is a preflight check for update operations. It does not explicitly name alternatives or exclusions, but the intended usage is clear enough.

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