Write Drake Bars

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

Given no annotations, the description carries the burden of explaining behavior. It discloses the output type ('short Drake-style lyrics') and the input ('what the user is going through'). This is honest about the tool being a text generation tool, though it could add nuance about creative liberties or tone.

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 a single, front-loaded sentence that conveys the core function. The second sentence 'Pass what the user is going through' is slightly redundant and could be clearer, but it is still concise. No wasted words, though the wording 'Pass' is a bit awkward.

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 low-complexity tool with one required parameter and no output schema, the description is sufficiently complete. It explains the input and output without needing to elaborate on return values or side effects. A minor gap is lack of specificity about 'Drake-style' (e.g., tone, length), but that is likely understood.

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?

Schema coverage is 100% with a clear description for the 'situation' parameter. The description adds the phrase 'Pass what the user is going through,' which rephrases the parameter's purpose but adds little new meaning beyond the schema's own example. The schema does the heavy lifting, so a 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 tool's function: 'Turn a situation or topic into short Drake-style lyrics.' This is specific with a verb ('turn') and resource ('situation/topic... into lyrics'). It distinguishes itself as a creative generation tool, and since there are no sibling tools, there is no ambiguity.

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 implies when to use the tool (when the user wants Drake-style lyrics based on a situation), but does not explicitly state exclusions or alternatives. With no sibling tools, there is no need for comparison, yet a clearer 'use when...' statement would improve guidance.

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