np_status

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

No annotations exist, and the description only states the tool returns status. It fails to disclose behavioral traits such as whether it is read-only, permission requirements, or response characteristics, placing full disclosure burden on the description.

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 concise, consisting of a single phrase. While there is no wasted text, it could be slightly more descriptive without harming conciseness. The structure is front-loaded but overly minimal.

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 many sibling tools and no output schema or annotations, the description is incomplete. It does not specify what 'status' includes, how the output is structured, or any limitations. For a simple zero-param tool, the description is minimally adequate but lacks needed context.

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, and schema coverage is 100% trivially. With no parameters, the description cannot add parameter-level meaning, but the lack of parameters makes this dimension less critical; thus baseline score of 4 is appropriate.

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' indicates the tool retrieves status information, but lacks a specific verb (e.g., 'get') and does not distinguish it from sibling tools like 'get_platform_status', which likely serves a similar purpose.

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 versus alternatives. Given many sibling tools, the absence of usage context reduces the agent's ability to select the correct tool.

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