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

Annotations already establish readOnly/idempotent/non-destructive/non-open-world, so the bar is lower. The description does add real behavior beyond them: a required scope (history:read) and explicit truncation/continuation for the export. However, phrases like "Current store, bounded filters/keysets; missing membership/claims stay explicit" are too cryptic to count as clear disclosure.

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 four sentences contain no filler, but they open with the least intelligible line (the API-contract reference) instead of front-loading a plain statement of what the export does. Density without orientation costs it clarity.

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 parameters and no output schema, safety is covered by annotations, but the description asserts truncation/continuation and "explicit" membership/claim handling without explaining how continuation is driven or what the output looks like. Adequate for invocation but leaves meaningful gaps.

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 takes zero parameters and schema coverage is 100%, so there is nothing for the description to clarify. Per the rubric this is the baseline 4.

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 leans on an opaque internal reference ("Same owner-private v2 contract as /api/me/asks") rather than plainly stating what the tool returns, so the actual purpose is carried mostly by the title. It does convey scope (owner-private history metadata export) and implicitly separates itself from research/payment/public-ledger siblings via the exclusion list, but the verb+resource framing is buried in jargon.

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?

It gives a prerequisite ("Explicit history:read required") but never states when to choose this over the many close siblings (history_owned_read, history_private_jobs_export, run_owner_export). The trailing exclusions ("No research, signer, payment, public-owner selector") hint at boundaries but are capability limits, not routing guidance to alternatives.

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