generate_json_schema

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

With no annotations, the description carries the full transparency burden. It discloses that the schema is not validated against at runtime, is bundled in the MCP tool rather than the core library, and exists purely to be handed back on request. This prevents false expectations about validation behavior.

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 most important information is front-loaded: what is returned, for whom, and why. The third sentence adds a useful caveat about runtime validation, but the .NET/JsonSchema.Net implementation aside makes it slightly more verbose than necessary.

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 zero-parameter tool with no output schema, the description is complete. It covers the return value, the relationship to related tools, the intended use, and an important limitation, so an agent has everything needed to call 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 input schema has zero parameters, so the description has no parameter semantics to add. Per the baseline rule for no-parameter tools, this is adequate; the description correctly focuses on return behavior instead.

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: 'Returns the raw JSON Schema (Json.schema.json)'. It further identifies the schema's relationship to generate_json and create_document_from_json, which clearly distinguishes it from the XML-schema sibling and from example generation.

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 explicitly names the intended audience and use case: callers authoring JSON by hand or script who want validation/autocomplete, rather than reverse-engineering from a generate_json example. It does not enumerate explicit 'when not to use' scenarios, but the context is clear enough.

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