np_status

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

With no annotations available, the description carries full responsibility for behavioral disclosure, but it only restates the concept of 'status' without mentioning read-only behavior, return format, permissions, or side effects. This leaves the agent without essential operational information.

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 extremely short but is under-specified rather than concise. A single phrase provides no structure or substantive content, similar to the 'Process' example, and does not 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?

The description is severely incomplete for a status tool. It does not define what 'platform and controller status' means, what the output contains, or how it relates to sibling status tools. No output schema exists, so the description was expected to compensate but fails to do so.

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 input schema has zero parameters, so the baseline is 4. Since there are no parameters to describe, the absence of parameter-specific information in the description is not a deficiency.

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 without an action verb, making it unclear what the tool does. It vaguely identifies the resource but does not distinguish it from sibling tools like get_platform_status or get_system_status.

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?

There is no guidance on when to use this tool versus alternatives such as wm_status, get_platform_status, or sensor_status. The description provides no context, exclusions, or alternative references.

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