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

With no annotations, the description should disclose behavioral traits. It only states that objects are 'public' which implies read-only, but it doesn't clarify how the 'about and contributed by' filter works, whether results are paginated, or any authentication requirements. This ambiguity limits the agent's ability to predict behavior.

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 brief (one sentence), but the phrasing is awkward and could be clearer. It does not waste words, but the ambiguity in 'about, and contributed by' reduces its effectiveness.

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?

Given the lack of an output schema and annotations, the description should provide more context about the return structure and behavior. It only mentions vague 'public objects' and the filter criteria, leaving the agent uncertain about the response format and exact query semantics.

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 input schema already includes a description for the 'sub' parameter, and the tool description does not add any additional meaning or usage context for it. With 100% schema coverage, the description provides no extra value for understanding the parameter.

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 identifies that the tool returns public objects tied to a Colony sub, but it lacks a clear verb (e.g., 'list' or 'get') and the phrase 'about, and contributed by' is ambiguous about whether both conditions apply or either. It does not clearly differentiate from sibling tools like search_collection.

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 for when to use this tool versus alternatives such as search_collection or list_collection. The description only states what the tool returns, not the intended use case or exclusions.

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