Autoload: last report (v1, deprecated)

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

Annotations already declare readOnly=true, destructive=false, idempotent=true, openWorld=true. Description adds detail on the returned data fields and confirms no parameters. No contradictions, and context about v2 format is helpful.

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 concise sentences: first clearly describes output, second provides deprecation guidance. Front-loaded, no wasted words, 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?

No output schema, but description lists key return fields (section_stats, listing_fees, events, feed_url). Sufficient for a simple read-only tool with no parameters. Could mention more structure but adequate.

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?

Zero parameters, so baseline is 4. Description confirms 'no parameters' and schema coverage is 100%. No additional parameter info needed.

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?

Description clearly states what the tool does: returns summary statistics of the last completed upload, listing specific fields (section_stats, listing_fees, events, feed_url). Differentiates from sibling v3 by explicitly marking as deprecated and pointing to the newer version.

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 informs the agent that this version is deprecated, explains the replacement (feeds_urls), and directs to use autoload_get_last_completed_report_v3. Provides clear when-not-to-use and alternative.

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