np_status

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

With no annotations, the description must carry the burden of disclosing behavior. The word 'Status' weakly implies a read-only operation, but the description does not explicitly state that it returns information, what information it provides, or whether any side effects exist. It adds very little 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?

The description is extremely short, but this is under-specification rather than effective conciseness. A single noun phrase without a verb or context does not earn its place; it reads like a title, not a functional description. There is no structure that helps an agent understand the tool's purpose.

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 presence of numerous sibling status tools, the description is not complete enough to disambiguate. It fails to explain what 'Platform & Controller' encompasses, what output to expect, or how this differs from get_system_status, get_platform_status, or other status tools. The lack of annotations and output schema makes this minimal description insufficient.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and there is no schema information to supplement. It cannot add value beyond the empty schema, so the baseline score holds.

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 is a noun phrase ('Platform & Controller Status') rather than a clear verb-action statement. It implies the tool reports status but does not explicitly state what it does (e.g., 'Retrieves current platform and controller status'). It also does not distinguish this from several sibling status tools like get_system_status, get_platform_status, or ovo_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 or how it differs from alternatives. With several status-related siblings, the description should mention that this is the go-to for platform/controller health or clarify its scope, but it omits any such context.

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