Overview of the entire nervous system - what it is, where it came from, how to implement it, what problems it solves, and operational stats.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | What to learn about. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not contradict these. It adds useful context about the tool's scope (entire nervous system) and the specific topics covered, but does not elaborate on operational behavior beyond what annotations provide.
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 front-loads the primary purpose and enumerates the covered topics. It is concise without being overly terse, though a bulleted list might improve scannability.
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 simple input schema (one enum parameter) and no output schema, the description covers the tool's purpose and available options sufficiently. It does not describe return format, but that is not critical for this tool. The description is complete enough for basic use.
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?
Schema coverage is 100% with a single parameter that uses an enum. The description enriches the schema by listing the exact topics (overview, origin story, etc.) that correspond to the enum values, providing clarity beyond the parameter's generic description 'What to learn about.'
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 states it provides an 'overview of the entire nervous system' covering multiple aspects, which clearly indicates the tool's purpose. However, it does not explicitly distinguish itself from sibling tools like get_framework or get_health_status, though the unique subject matter provides some differentiation.
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 gives no guidance on when to use this tool versus alternatives. There is no mention of context or exclusions, leaving the agent without direction on selecting this tool over others for specific information needs.
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 clearly distinct purposes, but there is some overlap among multiple audit/check tools (e.g., accountability_check, drift_audit, security_audit). However, descriptions and naming help differentiate their specific scopes, so ambiguity is low.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_archive_safety, propagate_family_member), making them predictable and easy to understand.
33 tools is on the high side, but the server covers a broad domain (system health, audits, propagation, session management, etc.). The count is justified by the comprehensive scope, though it may feel heavy for agents.
The tool set covers the entire lifecycle of system management: health monitoring, audits, propagation, sessions, compliance, and more. No obvious gaps for the stated purpose of a nervous system framework.
