manage_system

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

No annotations are present, so the description bears full responsibility for disclosing behavioral traits such as side effects, authorization needs, or destructive potential. The description provides none of this information, listing only action names.

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 run-on sentence with a long list of actions. It lacks structure, is not front-loaded with a clear purpose, and contains no paragraph breaks or bullet points. Every sentence should earn its place; here, the list is exhaustive but not helpful.

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 9 parameters and no output schema, the description should explain return values, usage patterns, or common workflows. Instead, it only lists action names and parameter associations. The tool is highly complex but the description provides almost no contextual completeness.

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 89%, so the baseline is 3. The description does add a list of which parameters are used by which actions (e.g., 'Used by: service_config_get'), but this information is already present in the schema's parameter descriptions. The description does not provide additional meaning beyond what the schema already conveys.

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 lists multiple actions but fails to state a unified purpose. It reads as an enumeration of sub-commands rather than a clear verb+resource. This makes it hard for an agent to understand when to invoke this tool versus siblings like 'manage_logs' or 'get_system_summary'.

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 on when to use this tool or when to prefer alternatives. The description merely lists actions without context, leaving the agent to guess the appropriate use case among 24 sibling tools.

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