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

The description notes that 'any Colony-authenticated agent may vouch' via a POST endpoint, but it does not disclose whether this tool itself performs the vouch, lists the objects, or something else. No annotations exist, so the description carries full burden, but it leaves behavioral traits ambiguous and fails to mention side effects, response format, or auth requirements for this 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 a single sentence that efficiently conveys the core domain concept. However, it packs a lot of information ('deposited', 'awaiting curation', 'vouch') in a way that may require unpacking, but it is not excessively verbose.

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 and no annotations, the description must fully explain the tool's behavior, but it does not state what the tool returns or what operation it performs. The vouch endpoint is mentioned but not in the context of this tool's function. This leaves significant gaps for an agent trying to invoke 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 tool has zero parameters, and the baseline for such cases is 4. The description adds no parameter details because there are none to describe, but it also does not introduce any confusion or conflict with the empty schema.

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 defines a resource ('Objects deposited and awaiting curation') but lacks a specific verb stating what the tool does (list, retrieve, vouch). It provides some distinction from siblings by mentioning the curation state, but the absence of an action leaves the purpose vague.

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?

No guidance is provided on when to use this tool versus alternatives like list_collection or search_collection. The mention of the vouch endpoint gives a hint about a related action, but it does not clarify when this tool should be chosen.

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