swagger_get_schema

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read-only 'Get' operation but omits any detail about response format, truncation, $ref resolution, or environment handling. It adds little behavioral context beyond the tool name.

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, direct sentence with no filler or repetition. It front-loads the action and object, though it is terse enough that it sacrifices some useful context.

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?

With no output schema and no annotations, the description does not explain what the tool returns, how errors or missing schemas are handled, or when it should be preferred over sibling tools. The parameter schema carries most of the operational burden, but the overall definition is not complete for deciding and invoking 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 input schema documents all four parameters with descriptions, giving 100% schema coverage, so the description does not need to repeat them. The description adds no extra parameter meaning beyond identifying the target as a schema/model, which maps to schemaName.

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 ('Get') and names a specific resource: a schema/model definition from Swagger documentation. This distinguishes it from sibling tools focused on endpoints or API requests, though it does not explicitly contrast itself with swagger_get_endpoint.

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 gives no guidance on when to use this tool versus alternatives like swagger_list_endpoints or swagger_get_endpoint. There are no prerequisites, exclusions, or workflow hints—only the tool name and noun phrase imply its purpose.

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