Get Business Insights

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

Beyond the readOnlyHint=true and openWorldHint=true annotations, the description adds valuable behavioral context: the return structure (url, sections, optional references) and an operational instruction that 'The LLM should parse the raw text in each section.' This helps the agent understand how to handle the output.

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 well-organized with clear sections (intro, note, args, returns) and is concise—no redundant sentences. Every line contributes to understanding the tool's purpose, restrictions, parameters, and output handling.

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 a single optional parameter, an existing output schema, and annotations, the description covers the essential operational aspects: purpose, account restriction, parameter values, return structure, and a parsing instruction. Minor gaps like error handling or examples are not critical for this simple read-only tool.

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 only shows time_range with a default, with 0% description coverage. The tool description compensates by specifying allowed values ('7d, 30d, 90d') and the default ('7d'), which is meaningful guidance beyond 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 clearly states a specific verb ('Get') and resource ('Business/Creator account insights from Professional Dashboard'). While it doesn't explicitly contrast with sibling insight tools like get_audience_insights, the reference to Professional Dashboard provides a distinct scope.

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 gives a clear prerequisite: 'Professional Dashboard is only available for Business and Creator accounts.' However, it provides no guidance on when to use this tool versus the other insight-specific tools (e.g., audience, content, activity), so alternatives are not addressed.

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