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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavior: limited free results, paid upgrade links, paid access via x402/Apify without an account, Bearer token billing with TidyTools credits, and specific rate limits. These details materially affect when and how an agent should invoke the tool.

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 front-loaded with the core purpose and then adds constraints, payment, auth, and rate limits in a compact form. It is dense but nearly every sentence carries operational value; the payment-path sentence is useful though slightly cluttered.

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?

For a one-parameter, read-only, open-world tool with no output schema, the description covers purpose, scope, exclusions, auth, billing, and rate limits. An agent has enough information to decide whether to call it and how to call it 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 schema already documents the single required parameter 'url' at 100% coverage, including that it must be a public HTTP(S) URL. The description reinforces the one-URL scope but adds little syntax or format detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Finds one public job posting from a company's jobs board.' It also scopes the tool to a single URL and explicitly excludes batch work and unrestricted monitoring, making it distinguishable from generic URL-fetching siblings.

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 gives clear usage constraints: 'Use for one url. Not for batch work or unrestricted monitoring.' It also states free-tier limits and the Authorization header needed for full results. It does not name a specific alternative sibling for batch work, which keeps it from a 5.

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