Read About ComOS — the Federation User Manual's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed about-us knowledge as markdown. Zero-arg; identity-free. Example: call about_us_about with arguments {}.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnly, idempotent, and non-destructive. The description adds that it returns markdown and is zero-arg, which aligns with the annotations. It provides a bit of extra context without contradicting the metadata.
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 fairly concise but has some redundancy (e.g., 'Read About ComOS' followed by 'Read-only' and 'Returns'). It is not overly verbose, but could be tightened without losing clarity.
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 simplicity of the tool and lack of an output schema, the description sufficiently indicates the return format (markdown) and the general content (about ComOS). It covers the essential information without needing further detail.
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 no parameters, and the description explicitly notes 'Zero-arg', making it clear that no arguments are needed. Although the schema already covers this, the description reinforces it effectively.
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 clearly states that the tool reads about ComOS and returns the knowledge as markdown. It is straightforward and distinguishes itself as an 'about' resource among the many sibling tools.
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 does not explicitly explain when to use this tool versus alternatives, but given its self-explanatory nature (fetching the about page), the intended use is implicit. Minimal guidance is provided beyond the read-only nature.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is overlap among introspection tools (introspection_system_probe vs. introspection_system_confidence vs. introspection_system_diff) and between similar reading tools (federation_canon_get vs. federation_tenant_info). Descriptions help clarify but boundaries are not always crisp.
Naming is inconsistent: some tools use verb_noun (federation_bond_post, federation_bond_release), some use noun_verb (federation_arena, federation_help), and some use noun_noun (about_us_about, moltbook_read). There are also tools with dot separators (about_us_about) and camelCase (cohort_email_send) mixed with snake_case, making patterns unpredictable.
With 72 tools, the surface is extremely large and likely to overwhelm agents. While the server covers a complex federation platform, this many tools suggest poor scoping or lack of consolidation, making it hard for agents to discover and choose the right tool.
The server covers core federation lifecycle (create/list/update/delete tenants, manage managers, bonds, keys) and some platform operations, but there are gaps such as missing tenant deletion workflow details, no explicit tool for updating manager info, and no direct tool for tenant-level settings beyond basic update. The introspection suite is thorough but the domain may not be evenly covered.
