vs_endpoints_get

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

Annotations already declare readOnlyHint: true, meaning it's a safe read operation. The description adds no additional behavioral context beyond the API path. It does not contradict annotations.

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?

Extremely concise: one sentence plus the API path. No wasted words, and information is front-loaded. Every part is relevant.

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 single-parameter get tool with output schema and annotations, the description is minimally adequate. It does not explain return values (though output schema exists) or any additional context needed for correct usage.

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?

Schema coverage is 100% and the input schema describes the only parameter (endpoint_id) as 'Vector Search endpoint ID or name'. The description adds no extra meaning beyond referencing it in the API path.

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?

Description explicitly states 'Get a Vector Search endpoint' with the specific API path, clearly indicating the verb (get) and resource (endpoint). It distinguishes from siblings like vs_endpoints_create, vs_endpoints_delete, and vs_endpoints_list.

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 on when to use this tool versus alternatives (e.g., vs_endpoints_list for listing all endpoints). The description does not mention prerequisites, context, or when to prefer this tool.

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