get_rack_context

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

With no annotations, the description must carry the behavioral burden, and it does by explicitly stating 'This tool performs no write operations' and describing the response as 'bounded'. It does not cover edge cases such as not-found behavior or authentication, but the central read-only side-effect guarantee is clearly disclosed.

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 two sentences with no redundant filler. It front-loads the action and resource, then adds the key behavioral guarantee, making every clause informative.

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 an output schema and no true schema-defined parameters, so the description covers most operational facts. However, the unresolved mismatch between the stated selection criteria and the empty input schema, along with the lack of any siblings routing, leaves an agent uncertain about how to actually invoke the tool.

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 declares zero properties, yet the description says the rack is selected 'by ID or exact site and rack name', implying parameters that are not present in the schema. The zero-parameter baseline would normally be 4, but the description introduces a misleading invocation contract that an agent cannot satisfy based on the provided schema.

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 uses a specific verb, 'Read', and names a precise resource: 'one exact NetBox rack'. It further specifies the returned content ('bounded device elevation summary' and 'recorded power-feed count'), making the tool's purpose clear and distinct from sibling tools that target devices, sites, connectivity, or power paths.

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 establishes a clear usage context: exact single-rack lookup by ID or exact site and rack name. It does not explicitly name alternatives or state when not to use this tool, so it falls short of full routing guidance, but the intended scenario is understandable.

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