headline

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

No annotations are given, and the description '{d}' offers no behavioral traits. The tool's side effects, permissions, or response format are completely unspecified.

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 too minimal ('{d}'), which is under-specification rather than conciseness. It fails to provide necessary information.

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?

Despite having an output schema, the description is missing, leaving the tool's behavior largely undefined. The context is incomplete for effective use.

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 description adds no meaning to the parameters. Although the schema includes defaults for 'desc' and 'params_desc', the description itself does not explain any parameter beyond what is in 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 is a placeholder '{d}' and does not define the tool's purpose. The name 'headline' suggests headline generation, but the description provides no clarity.

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?

No usage guidance is provided. The description lacks any context on when to use this tool versus its many siblings like 'generate_slogan' or 'create_metaphor'.

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