brandbillboard

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'brandBillboard' reveals nothing about whether this is a read or write operation, what data it accesses, what permissions are needed, rate limits, or expected behavior. This complete lack of transparency warrants a score of 1.

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?

While technically concise with just one word, this is under-specification rather than effective brevity. The description fails to convey any useful information and doesn't follow a structured format. It earns a low score because conciseness should not come at the cost of complete information omission.

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 unknown complexity (no output schema, no annotations, no parameters), the description is completely inadequate. It provides no information about what the tool does, when to use it, or what it returns. For any non-trivial tool, this level of incompleteness is unacceptable.

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 tool has 0 parameters with 100% schema description coverage, meaning the schema fully documents the absence of parameters. The description doesn't need to compensate for any parameter gaps. While it adds no parameter information beyond the schema, the baseline for zero parameters with complete schema coverage is 4.

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?

Tautological: description restates name/title.

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 offers absolutely no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or comparison to sibling tools like 'billboardaweme' or 'brandweeklylist'. Without any usage information, this score must be 1.

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