Site or page age

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

The description explicitly warns that the operation 'may consume SEO Intellect account limits,' which is a valuable behavioral caveat beyond what annotations state. It also identifies the upstream API tool, though it does not describe other side effects; the annotations already indicate no destructive behavior.

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?

Three short sentences with the core purpose front-loaded and the account-limit warning placed last. The 'Upstream API tool: site-age' sentence is mildly useful provenance but not essential; otherwise every sentence earns its place.

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 description does not explain the async/task_id flow or the shape of the returned indexing date, relying on rich schema descriptions for parameters. With no output schema, a bit more detail about result semantics would make it complete, but the main behavior is clear.

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 description adds no parameter-specific semantics, but the schema descriptions cover 100% of the properties, including timeout, wait_for_result, poll_interval_ms, and task_id. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 names a specific action and resource: 'Find the first known indexing date for URLs.' This is clear and distinguishes the tool's core purpose from many siblings, though it does not explicitly contrast it with tools like page_index or positions.

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 no explicit guidance on when to use this tool versus alternatives, and no when-not-to-use conditions. The only implied usage is 'use it to find a URL's first indexing date.'

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