Get KIT operation schema

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

Despite the readOnlyHint annotation already indicating a safe read, the description goes further by detailing the complete return payload: HTTP method, path, parameters, content type, pagination info, and dereferenced schemas. It also clarifies the operational purpose ('to learn the exact body shape'), which adds value beyond the annotation.

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?

Two sentences, no redundancy. The first sentence enumerates the return contents, the second gives usage instruction. Every word earns its place.

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 single-parameter tool with no output schema, the description is fully self-sufficient: it explains what the tool returns and when to call it. The absence of an output schema is compensated by explicitly listing the metadata components returned.

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 description for the single parameter operation_id is thorough, including format (PascalCase), an example, and a pointer to search_operations. The description itself does not add parameter-specific detail beyond this; it only contextualizes the parameter's use. Since schema coverage is 100%, a baseline of 3 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 opens with a specific verb and resource: 'Get full metadata for one KIT API operation by operationId.' It lists exactly what is returned (HTTP method, path, parameters, schemas) and explicitly distinguishes itself from siblings by instructing to call it before kit_request or create/update tools.

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 second sentence provides explicit usage guidance: 'Call this before kit_request or any create/update tool to learn the exact body shape.' This names the exact context and tools it pairs with, making it clear when to use this tool instead of guessing.

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