siteprofiler_backlink_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get' which implies a read operation, but it doesn't disclose auth requirements, rate limits, pagination, or the structure of the returned backlink profile. This is a significant gap for a tool with no annotations.

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 a single concise sentence, front-loaded with the key action and resource. It earns its place without waste, but it's so brief that it omits important context, preventing a 5.

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?

With no annotations and no output schema, the description must explain what the tool returns and under what conditions. It only says 'Get SiteProfiler backlink profile' without mentioning the required URL (not listed as required in the schema), the response format, or what kind of profile data is included. This is inadequate for an agent to confidently invoke the tool correctly.

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 has 100% coverage with descriptions for all three parameters (url, body, query), so the baseline is 3. The description adds no additional parameter semantics, but it doesn't need to since the schema already explains them clearly.

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 'Get SiteProfiler backlink profile' uses a clear verb ('Get') and a specific resource ('SiteProfiler backlink profile'), which distinguishes it from sibling tools like siteprofiler_overview or siteprofiler_competitors. However, it doesn't elaborate on what the backlink profile includes or how it differs from the overview, so it's not as explicit as it could be.

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 other siteprofiler tools. It doesn't mention whether a URL is required, what kind of URLs are supported, or any preconditions. The description simply states the action without contextual cues.

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