get_contests_with_broken_images

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates a read-only fetch operation and the return purpose, but does not mention pagination behavior (despite skip/batch_size params), authentication requirements, or other side effects. The word 'Fetch' implies read-only, providing a moderate level of transparency.

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 consists of two concise sentences, front-loaded with the action and condition. Every sentence adds value without unnecessary filler, making it appropriately sized and 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 simplicity and the presence of an output schema, the description sufficiently covers core behavior and purpose. It lacks parameter detail but is otherwise complete for this niche fetch operation, making it adequate for an agent to understand when and why to use it.

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?

The input schema lists skip and batch_size with defaults but no descriptions, and the tool description does not explain these parameters in context. With 0% schema description coverage, the description fails to compensate for the missing parameter semantics, leaving the agent to infer their meaning.

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 verb 'Fetch' and the targeted resource 'contests' with a specific filter condition ('image.primary.status is marked as broken'). This distinguishes it from sibling tools like get_contests_missing_images, which addresses a different condition.

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?

It provides a clear context by explaining the intended use case: 'so the chatbot can display or re-generate banners'. While it does not explicitly mention alternatives or when not to use the tool, the specific condition implies a focused scenario, giving acceptable guidance.

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