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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves most of it unstated. It does not disclose that the call can mutate the world when ingest_into_world is true, does not explain what 'sanitized' means in practice, and says nothing about permissions, failure modes, or latency/rate limits for an external connector call.

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?

It is a single front-loaded sentence with no filler, and the action plus resource lead immediately. It is arguably too terse for the amount of unstated behavior, but the sentence itself 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 four-parameter tool with no annotations and no output schema, the description omits the two things an agent most needs: the side effect of ingest_into_world persisting axioms into the world, and any sense of what the returned 'sanitized ground-truth facts' look like. The mutation semantics are left entirely to the schema.

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 100%, with all four parameters documented including the ingest_into_world default, so the schema already does the heavy lifting. The description adds no parameter-level meaning beyond it, which makes the baseline 3 correct rather than a deduction.

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 names a specific verb ('Execute'), a specific resource ('a registered Custom Epistemic Connector'), its target ('on a Small World'), and the outcome ('return sanitized ground-truth facts'). This clearly separates it from syntropy_register_connector or syntropy_list_connectors, though it never explicitly contrasts itself with a named sibling.

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?

There is no explicit when-to-use or when-not-to-use guidance. The word 'registered' hints at a prerequisite, but the description never says to register first, never mentions alternatives such as syntropy_ingest_axioms for facts already known, and never states the condition under which ingestion should be preferred over a read-only query.

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