billboardaweme

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it gives no information about whether this tool performs read or write operations, its side effects, authentication needs, rate limits, or expected outputs. The single-word description fails to provide any behavioral context.

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 the description is extremely concise with just one word, it is under-specified rather than efficiently informative. Conciseness should not come at the cost of clarity; this description fails to communicate essential information, making it ineffective despite its brevity.

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 lack of annotations and output schema, the description is completely inadequate. It provides no insight into the tool's functionality, behavior, or output, leaving the agent unable to understand or use it effectively. The context signals do not compensate for this deficiency.

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 0 parameters with 100% coverage, meaning no parameters need documentation. The description does not add parameter semantics, but this is acceptable since there are no parameters to explain. A baseline score of 4 is appropriate as the schema fully covers the lack of parameters.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'aweme', 'brandbillboard', 'hotlist', and 'chart' that might serve related functions, there is no indication of context, prerequisites, or differentiation. This leaves the agent with no usage information.

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