bh_generate_ideas

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

With no annotations, the description carries the disclosure burden. It does disclose the key behavioral outcome: exactly 5 unique angles will be generated. It does not mention output format, nondeterminism, or whether the operation has side effects, but for a non-destructive brainstorming tool this is a reasonable baseline.

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?

One short sentence, front-loaded with the action and deliverable. 'using AI' is mildly redundant in context but does not distract from the core message.

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 single-parameter tool with full schema coverage, the description is adequate to decide when to call it. However, with no output schema, it would benefit from a note about what the response looks like and how the five angles are presented.

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 description coverage is 100%, and the only parameter, 'topic', is already described as 'Topic to brainstorm ideas about'. The description adds the 'blog post angles' context but does not need to compensate for missing schema information.

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 names a specific verb ('Brainstorm'), a concrete deliverable ('5 unique blog post angles'), and the input type ('topic'). It is clear about scope, though it does not explicitly contrast with siblings such as bh_discover_topics.

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?

Usage is implied by the verb 'brainstorm' and the target 'blog post angles': use this when you need ideation for a topic. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named, so an agent has to infer when this is preferred over siblings like bh_discover_topics.

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