export_schema

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, and it does not deliver. It never states whether the operation is read-only, which formats are supported, what the output looks like, or how the registry/context/version parameters affect 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 description is a single front-loaded sentence with no wasted words. However, it is under-specified rather than efficiently informative; a few more sentences were required to make it useful.

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 tool with 5 parameters, 0% schema coverage, no annotations, and no output schema, the description provides only a headline. An agent cannot determine allowed formats, the return shape, or the roles of the optional parameters without opening other tools or guessing.

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 description coverage is 0%, so the description must compensate. It loosely maps to two parameters—'a single schema' (subject) and 'the specified format' (format)—but says nothing about context, registry, or version, which remain completely unexplained.

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 states a clear verb and resource—'Export a single schema'—and adds a distinguishing manner, 'in the specified format,' which hints at serialization/conversion rather than plain retrieval. However, it does not explicitly differentiate from siblings like get_schema, get_schema_by_id, or export_subject, leaving some ambiguity about what 'export' adds.

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 is given on when to use this tool versus alternatives such as get_schema, get_schema_versions, or export_subject. There are no usage conditions, exclusions, or named alternatives, so the agent must infer the tool's niche from its name alone.

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