list_business_scenarios

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

With no annotations provided, the description carries the burden. It discloses the output format (curated list with matching smart queries and expected ROI) and lists covered business areas, giving a good sense of what to expect. It does not mention side effects or safety, but the 'list' verb implies a read-only operation. Missing details like pagination or depth are minor for this type of tool.

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 mostly concise with structured sections for Business Areas and Output. However, it includes a placeholder 'Example: {}' that is empty and adds no value, violating the principle that every sentence should earn its place. This reduces the overall quality.

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 has no parameters, no output schema, and no annotations, the description provides enough context about what the tool returns and which business domains it covers. The empty example placeholder is a minor gap, but for a simple discovery tool, the description is adequate 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 tool has zero parameters, and the schema coverage is 100% (trivially). The baseline for 0 params is 4, and the description doesn't need to explain any parameter behavior. It adds no parameter-related information, but none is required.

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: 'List common business scenarios and their recommended smart query solutions.' It uses a specific verb (list) and resource (business scenarios) and differentiates from siblings like get_smart_queries, which focuses on queries rather than scenarios. The business areas and output type add specificity.

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?

It provides a clear use case: 'Perfect for discovering workflow automation opportunities.' However, it does not explicitly mention when not to use it or compare it to alternatives like get_smart_queries or list_tool_categories, so it lacks exclusionary guidance.

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