np_status

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

No annotations are provided, and the description is just a title. It doesn't disclose whether the operation is read-only, what output to expect, whether it has side effects, or any other behavioral traits, leaving the agent with no information beyond the tool's name.

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?

While the description is extremely short, it is under-specified rather than concise. It is a fragment that provides no actionable information, so it fails to earn its place as a useful description.

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?

With no schema, no output schema, and no annotations, the description is the only source of context. Its single phrase is insufficient to understand the tool's purpose, output, or relationship to the many sibling status tools.

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 accepts zero parameters, and the schema is empty. Since there are no parameters to document, the description doesn't need to add parameter semantics; the baseline for 0 params is 4.

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 'NeuroPlatform v2 — Platform & Controller Status' is a noun phrase lacking a clear verb, so it doesn't explicitly state what the tool does (e.g., 'get' or 'retrieve'). It also doesn't distinguish itself from sibling tools like 'get_platform_status' or 'wm_status', which likely serve similar status-reporting roles.

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 provides no context about when to use this tool versus alternatives. There are multiple status-related siblings (get_platform_status, get_system_status, wm_status), and no guidance is offered to choose among them.

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