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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the auth mechanism (Authorization: Bearer tt_…), billing model (TidyTools credits), x402 payment path with no Apify account, and concrete free-tier rate limits. This is exactly the operational context an agent needs before calling.

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?

Purpose is front-loaded and each sentence conveys actionable information about payment, auth, or limits. The x402/Apify sentence is slightly dense but still earns its place for callers who need paid access.

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 output schema, the description signals the return shape (limited free result plus paid upgrade links) and covers auth and rate limits thoroughly. It doesn't detail what authority metrics are actually returned, a minor gap for this complexity level.

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 coverage is 100% and both domain and url are documented with their alias relationship, so the schema carries the load. The description only reinforces 'one domain' without adding format or validation detail beyond the schema, matching the baseline 3.

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?

States a specific verb and resource: 'Looks up open-data authority for one domain', which is distinct from sibling tools like domain_whois or traffic_rank. It doesn't explicitly name which sibling to use instead for related lookups, so the differentiation is partial.

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?

Explicitly scopes usage to one domain and excludes batch work and unrestricted monitoring, which is clear when-not guidance. It stops short of naming alternatives (e.g., domain_overview) for those excluded cases.

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