run_connector_conformance

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

There are no annotations describing side effects, read-only behavior, or failure modes. The description does not explain whether checking live schemas can mutate anything, what happens on drift, or how results are returned.

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 concise sentence with no redundancy or filler. It front-loads the primary action and purpose effectively.

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?

The tool is simple, but the description omits expected output, return format, and behavioral details. An agent knows the intent but not what a successful or failing invocation looks like or what the boolean actually controls.

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 single boolean parameter 'check_live_schemas' has no schema description and the tool description adds no meaning to it. With 0% schema coverage, the parameter's effect is entirely unexplained beyond its name and default value.

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 clearly states a verb ('Check') and a resource ('every primitive provider'), with the goal of detecting hosted Tool schema drift. It is reasonably distinct from sibling tools like list_connectors or connector-specific tools, though 'primitive provider' is somewhat vague.

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 provided about when to use this tool versus alternatives such as list_connectors or individual connector inspection tools. There is no mention of prerequisites, expected context, or when not to use it.

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