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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description does add useful traits beyond that (results ordered newest first, and each item carries phase and entry counts). However, it does not say whether results are paginated, capped, or filtered, which is the main behavioral unknown for a list endpoint.

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?

One sentence, front-loaded with the verb and resource, then the ordering and return content. Nothing redundant or padded.

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?

For a one-parameter read-only list tool with full schema coverage and no output schema, this covers what the agent needs to select and call it. The remaining gap is whether the result set is bounded or paginated, which the agent cannot determine from the description.

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?

There is a single parameter and schema description coverage is 100%, so the schema already explains brandId as the owning project. The description's phrase 'a brand's giveaways' only echoes that relationship, adding no format, constraint, or edge-case information.

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 gives a specific verb and resource ('List a brand's giveaways') and adds scope, ordering, and returned fields, which separates it in practice from get_giveaway and list_giveaway_entries. It does not name those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied: call this to enumerate all giveaways belonging to a brand, rather than fetching one giveaway or its entries. There is no explicit when-to-use/when-not statement and no guidance on how this relates to create_giveaway, update_giveaway, or draw_winners workflows.

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