siteprofiler_audience

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'get' which implies a read operation, but gives no details about request behavior, response format, rate limits, or any side effects. This is insufficient for a tool with zero annotation coverage.

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 extremely terse, consisting of one short sentence. While it is not verbose, it is under-specified and lacks the structure needed to convey necessary information about a tool with optional parameters and multiple sibling tools.

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?

The tool has three optional parameters, no output schema, and many sibling tools in the same product family. The description provides almost no context about what audience data is returned, how to use the parameters, or how this tool relates to siteprofiler_overview or siteprofiler_competitors. This is far from complete.

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 documents all three parameters with descriptions, achieving 100% schema_description_coverage. However, the descriptions for 'body' and 'query' are generic passthrough boilerplate, not specific to audience data. The description text adds no additional parameter meaning, so a baseline of 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 uses a clear verb 'Get' and identifies the resource as 'SiteProfiler audience data', which aligns with the tool name. However, it does not explain what 'audience data' includes or distinguish this tool from sibling siteprofiler_* tools like siteprofiler_overview or siteprofiler_competitors.

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?

There is no guidance on when to use this tool versus alternatives. The description is a single statement with no context about typical use cases, prerequisites, or when other tools would be more appropriate.

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