Get Audience Insights

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

Even though readOnlyHint and openWorldHint are present, the description adds valuable behavioral context: it describes the return format (Dict with url, sections, references) and explicitly instructs the LLM to parse raw text to extract audience demographics. This goes beyond the annotations and sets expectations for post-processing.

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 concise and well-structured: a clear one-line purpose, a relevant availability note, and a compact Args/Returns section. Every sentence adds value, and the format is easy to scan for an AI agent.

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 tool with no input parameters and an output schema (though not shown), the description fully specifies what the agent should expect: the return structure and the need to parse raw text. It also covers an important prerequisite (account type availability), making it complete for its simplicity.

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, so the baseline is 4. The description lists 'ctx: FastMCP context for progress reporting' as an argument, but this is not reflected in the empty input schema and is likely framework-injected. It adds no confusion about real user parameters since there are none, so the baseline holds.

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: 'Get audience demographics from Professional Dashboard.' It uses a specific verb and resource, and the scope ('Professional Dashboard') distinguishes it from sibling insights tools like get_business_insights or get_activity_insights.

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 provides clear context by noting that Professional Dashboard is only available for Business and Creator accounts, which helps decide when the tool applies. It does not explicitly mention alternatives or exclusion cases, but the availability note is strong contextual guidance.

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