info

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get information', which implies a read-only operation, but it doesn't state whether it requires authentication, makes network calls, or has any side effects. It also doesn't mention how the information is structured or any limitations. The description is too sparse to be transparent.

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 a single sentence, extremely concise, and front-loaded with the verb 'Get information'. Every word adds value, and there is no wasted text. It is appropriately sized for a simple informational tool.

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 tool has no parameters and an output schema exists, so the description doesn't need to explain return values. However, it lacks context about what 'Neptune' refers to, what kind of 'information' is available, and how this tool relates to the deployment management workflow. Given its simple nature, the description is marginally adequate but could benefit from a brief example or clarification.

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 description is not required to explain parameter details. The input schema is empty, and the description adds no parameter information. Per the baseline for 0 parameters, a score of 4 is appropriate since there is no parameter semantics burden.

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 states a clear action ('Get information') and identifies the resource ('Neptune and available tools for cloud deployment management'). It distinguishes itself from sibling tools that perform specific operations (list_projects, get_logs, etc.) by being a general informational tool. However, it is vague about what kind of information is returned or how deep the coverage is.

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 implies that the tool is for retrieving information about the Neptune platform and its toolset, but it does not explicitly state when to use it versus alternatives. No exclusions or alternative tool mentions are provided. For a meta/informational tool, this is acceptable but could be clearer.

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