get_info

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

With no annotations, description correctly describes the tool as retrieving data and lists categories, but does not explicitly state it is read-only or has no side effects. Adequate but not thorough.

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 sentences with zero waste; first sentence is a clear verb-resource statement, second sentence adds actionable filtering detail.

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 no output schema, the description sufficiently summarizes expected return content (all health data categories) and optional filtering. Lacks mention of output format (text vs JSON) but acceptable for a simple retrieval tool.

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 covers 100% of parameters, but description adds concrete list of allowed section values and clarifies that instanceId is optional override, providing meaning beyond schema descriptions.

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?

Clearly states the tool retrieves INFO stats for the active instance, listing specific health data categories (memory, clients, etc.), which differentiates it from more specific sibling tools like get_health or get_memory.

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?

Gives implied usage via optional section filtering but lacks explicit guidance on when to use this tool versus siblings like get_health or get_memory. No 'when not to use' or alternative naming.

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