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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a read-only browse operation, enumerates return fields ('brief title, brand name, description, and brief ID'), and clarifies the exclusion of products for sale. It does not mention pagination or error conditions, but for a simple listing tool this is sufficient.

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 concise and well-structured, starting with the core purpose and moving through exclusions, usage triggers, return values, and cross-tool instructions. Every sentence earns its place, making it easy to scan quickly.

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 simple list tool with one optional parameter and no output schema, the description is complete. It explains what the tool lists, what it does not list, when to call it, what it returns, and how to use the result with submit_design. No critical information is missing for an agent to select and invoke the tool correctly.

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 has 100% coverage for the sole parameter brand_slug, so the schema already documents it. The description does not add any extra semantic meaning about the parameter itself. The cross-reference to submit_design concerns the output, not the input, so the description adds no parameter-level value 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 uses a specific verb and resource: 'List open design briefs, creative challenges and collaboration requests'. It clearly distinguishes from siblings by stating 'These are NOT products for sale' and referencing list_drops as the alternative for products. This makes the tool's purpose unambiguous and distinct from list_brands and list_drops.

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?

Explicit guidance is provided: 'Call this when asked about briefs, collaborations, creative challenges, or what brands are looking for.' It also names an alternative: 'To see products for sale, use list_drops instead.' Additionally, it instructs how to use the output: 'Use a brief ID with submit_design to respond.' This fully covers when and how to use the tool.

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