List official EQL press assets

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

The description discloses that the tool returns only metadata and links, not binary assets, which adds behavioral context beyond what annotations (none provided) would convey. This helps the agent understand the tool's scope of work.

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 two sentences long, with no redundant information. The first sentence states the primary action, and the second sentence clarifies constraints, making it efficient and front-loaded.

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 simplicity of the tool (one parameter, no output schema), the description adequately covers the return type (metadata and links) and what it excludes (downloads). No further details are necessary for an agent to use 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% description coverage, with a single parameter 'kind' described via an enum. The tool description does not add any additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 (list), resource (press assets), and scope (official Daybreak, for EQL). It distinguishes itself from sibling tools by specifying its focus on press assets, such as logos, artwork, screenshots, etc., which are not covered by other tools like eql_official_article or eql_wiki_page.

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 description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. The agent can infer usage from the purpose, but lacking explicit context reduces the score.

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