Read MOJOMO's capability manifest to learn the platform, agent actions, tethering policy, scopes, and rate limits before starting; no authentication required.
Read MOJOMO's capability manifest: what the platform is, what an agent can do here, the tethering policy, available scopes, and rate limits. Call this first. No auth required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden and does disclose the key operational fact that no auth is required, plus the scope of what is returned. It stops short of describing the return structure or whether the manifest is static, but the essential call-safety information is present.
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?
Two compact sentences: the first defines the resource and its contents, the second delivers the call-first directive and the auth fact. Front-loaded with zero filler.
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 bootstrap tool with no output schema, the description enumerates exactly what sections the agent will receive, which is precisely the information needed to decide to call it. Nothing material is absent.
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 the baseline is 4; there is nothing for the schema to document and nothing missing from the description on this dimension.
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?
States a specific verb and resource ('Read MOJOMO's capability manifest') and enumerates contents (platform identity, agent capabilities, tethering policy, scopes, rate limits). No sibling tool overlaps this read-only bootstrap role, so it is unmistakable.
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 first' gives an explicit ordering directive that an agent can act on without inference. It doesn't discuss when not to call or alternatives, but no sibling offers this content, so there is little to disambiguate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.