get_host_promo_codes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds an ownership scope ('you're hosting') and briefly describes the return shape (list of objects with code, discount, usage limits), enriching the annotation-only safety profile.

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 terse sentences: the first states purpose and scope, the second states the return type. No filler or redundancy; front-loaded and easily scannable.

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 presence of a rich schema, good annotations, and an output schema, this description covers the essentials: what the tool does, for whom, and the high-level result. Nothing critical is missing for this simple read-only tool.

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 100% for both parameters (event_id, fields), and the fields parameter lists all available dot-path options. The description's mention of 'code, discount, usage limits' only paraphrases the schema, adding no new semantic depth. Baseline 3 applies.

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 uses a specific verb ('Get'), names the resource ('promo codes'), and scopes it ('for a Partiful event you're hosting'). It clearly distinguishes this tool from siblings, none of which handle promo codes.

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 'you're hosting' provides clear context for when to use the tool (only for events you host) and implies it's the dedicated promo-code retrieval tool. No explicit exclusions or alternatives are given, but the context is sufficient for such a unique operation.

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