Get Domain Authority History

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

The description discloses that the target is resolved to PLD, which is a behavioral trait. No annotations exist, so the description carries the burden. However, it does not mention data freshness, rate limits, or what happens if no history is available.

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?

Two sentences, no redundant information. Clearly describes core functionality and key behavioral detail. Efficient and front-loaded.

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?

While the tool has 4 parameters with good schema coverage, the description does not mention return format, ordering, bounds, or pagination. With no output schema, more detail about the returned data structure would improve completeness.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value beyond schema, only clarifying PLD resolution which is already implied in the schema's description 'PLD is extracted'. No additional context for date range or granularity.

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 it returns historical Domain InLink Rank values for a target domain and explains PLD resolution. This distinguishes it from siblings like getDomainAuthority (current) and getPageAuthorityHistory (page-level).

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 implies use for historical authority data but does not explicitly specify when to use this tool versus alternatives like getDomainAuthority for current values or getPageAuthorityHistory for page history. No when-not-to-use or exclusion criteria are given.

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