Describe model endpoint

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it reports reachability and models, which implies a read-only operation, but it does not explicitly say there are no side effects or describe error handling or edge cases (e.g., what happens if the endpoint is not found). The description is adequate but could be more transparent about potential failure modes.

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, concise sentence that front-loads the core purpose and outcome. There is zero waste; every word contributes to understanding what the tool does. It is well-structured and easy to parse quickly.

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?

For a simple tool with one parameter and no output schema, the description is nearly complete. It specifies what the tool does and what it reports (reachability and models), which covers the return value expectation. It does not mention error handling or prerequisites, but those are minor given the simplicity and the fact that the parameter schema points to list_local_models. Overall, the description is sufficient for an agent to use it correctly.

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 schema has 100% coverage of the single parameter endpointId, with a clear description indicating where to obtain the id. The tool description adds no additional parameter semantics beyond what the schema already provides. Since coverage is high, the baseline of 3 is appropriate, and the description does not need to compensate.

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 clearly states the action (inspect), the resource (one configured endpoint by id), and the outcome (report reachability and models). It distinguishes itself from siblings by specifying that it inspects a single endpoint and reports on reachability and exposed models, which is different from listing all endpoints or getting configuration details.

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 this tool is used when you have a specific endpoint id and want to know if it's reachable and what models it exposes. It does not explicitly mention alternatives or exclusions, but the purpose is clear enough that an agent would know when to use it. The parameter schema further directs the user to get the id from list_local_models, providing implicit context.

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