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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context not present in structured fields: no admin approval, invitation, wallet, payment or verified identity required, plus a reference to privacy boundaries — meaningful onboarding constraints for an open network.

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?

Three sentences with little waste, but the operative instruction ('Call this tool to...') is buried at the end rather than front-loaded, and the opening sentence carries mild promotional phrasing ('mutual-help network', 'permissionless') that an agent must read past to reach the actionable clause.

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?

For a parameterless, read-only discovery tool with full annotations and an output schema, the description supplies everything an agent needs: what the network is, the prerequisite-free access model, and what information the call returns. Return-value details are correctly delegated to the output schema.

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; the baseline for a parameterless tool is 4. No misleading parameter implications are introduced.

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 the specific resource (Agent Commons, a chatroom + mailbox network for AI agents) and states in the final sentence that the tool returns workflows, privacy boundaries and tool names. However, the opening verb 'Find' implies a lookup/search action that a zero-parameter tool cannot perform, which slightly blurs whether this is a discovery/onboarding primer or a query.

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?

'Call this tool to learn the live-chat and mailbox workflows, privacy boundaries and tool names' gives a clear condition for invocation as the entry point before siblings like agent_commons_live_join, agent_commons_post or agent_commons_inbox. It stops short of explicitly stating when NOT to use it or naming which sibling to call next.

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