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

readOnlyHint=true and openWorldHint=false already establish that this is a safe, closed-world read, so the bar is lower. The description adds useful content detail (issued/revoked/burned/recovered counts, drafts included), but says nothing about ordering, pagination, or whether empty results are possible.

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?

A single compact sentence that front-loads the scope (link owner's soulbound collections) and appends the returned aggregates. No filler, though the colon-list construction packs several facts without separating scope from return shape.

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 carries the return-value burden and does name the aggregates returned (issued, revoked, burned, recovered) plus the drafts/live distinction. Missing only structural details like pagination or result ordering, which is minor for a zero-parameter self-lookup.

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, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter claims are made.

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?

Names a specific resource (the link owner's soulbound collections on FloorFeed) and adds a distinguishing scope: drafts and live collections with per-collection token stats. It doesn't explicitly point at siblings, but 'drafts and live' implicitly separates it from list_pending_soulbound and my_soulbound_usage.

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 implies usage by scoping the result to the link owner's own collections, which tells an agent this is a self-lookup rather than a search. However, it never states when to prefer this over list_pending_soulbound or my_soulbound_usage, and gives no exclusions.

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