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

With no annotations, the description carries the full burden. It adds real behavioral context beyond the schema: the templateId/campaignId mutual exclusivity and the caveat that seed is only honored "where supported." It still says nothing about permissions, whether the table goes live immediately or must be started via ad_start_table, or what is 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?

Front-loaded with the action, then each parameter in a compact semicolon-separated clause. Dense but every clause carries information; only the repeated "sunken-bell" example is redundant with the schema.

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 five-parameter mutation tool with no annotations and no output schema, the description covers all parameters but leaves the lifecycle (create vs. start) and the return shape entirely unaddressed. Adequate to invoke, incomplete for an agent reasoning about what happens next.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: templateId and campaignId are framed as alternatives, and seed is qualified as conditionally supported. The "sunken-bell" example duplicates the schema field description, but the exclusivity rule is net-new 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?

Opens with a specific verb+resource ("Create a table"), which is unambiguous against siblings like ad_create_character, ad_join_table, and ad_get_table. It doesn't explicitly contrast itself with ad_join_table or ad_start_table, but the name-plus-verb combination makes the scope obvious.

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 does give one genuinely useful selection rule — use templateId to launch from a template, or campaignId to attach an existing campaign "instead" — which tells the agent the two are alternatives. But there is no guidance on when to create a new table versus joining/spectating an existing one, and no prerequisites (e.g., whether registration is needed first).

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