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

With no annotations, the description carries the full burden. It usefully discloses the upsert-like semantics -- an insert matching an existing primary_key value replaces that row -- and the allowed column-type set. However, it omits what happens to existing rows and data when a schema is replaced, whether the operation is idempotent, and any error/permission 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?

A tight two-clause sentence with the main action front-loaded and the type grammar and primary_key rule appended as necessary detail. No filler, though the embedded JSON grammar makes it dense to parse.

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 schema-mutating tool with no annotations and no output schema, the core declaration semantics are covered, but the consequences of 'replace the schema' on existing rows and data -- the riskiest aspect -- are left unexplained.

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%, so the parameters are already documented. The description restates the type map and the primary_key-in-schema constraint rather than adding format, defaults, or edge cases beyond the schema, so the baseline 3 applies.

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 and resource -- 'Declare (or replace the schema of) a table in this tenant's state store' -- and is unambiguous against siblings like host.state.table_drop, host.state.insert, and host.state.set, each of which does something different to the same store.

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?

It implies when the tool applies (declaring a new table or replacing an existing table's schema), but never states when to prefer it over alternatives such as host.state.table_drop for removal or how declaring relates to subsequent host.state.insert calls. Usage must be inferred.

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