Create Wiki grid

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds genuinely useful context beyond that: the grid is created with no rows or columns, the created grid is returned, and subsequent writes must send back its ``revision`` (optimistic-concurrency behavior). It does not mention permission requirements, but the revision contract is valuable disclosure.

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?

Three short sentences, front-loaded with the core action, then the follow-up tooling and the return/revision contract. No filler and every sentence carries distinct information.

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?

No output schema exists, and the description compensates by describing the return value and the revision contract for later writes. Combined with full schema coverage and annotations, an agent has everything needed to invoke this create tool correctly.

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 single ``body`` parameter (title plus page by id or slug) is fully documented in the schema. The description adds no parameter-level detail (no mention of title/page/identifier semantics), so baseline 3 is appropriate.

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?

States a specific verb (create) and resource (an empty dynamic table/grid as a page resource), and explicitly distinguishes the result from the sibling tools that populate it. An agent can tell it apart from wiki_grids_update, wiki_grids_clone and wiki_grids_rows_create without opening a schema.

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?

Gives clear sequencing guidance: the grid starts empty and rows/columns must be added afterwards via grids_columns_create and grids_rows_create. It routes the agent to the correct follow-up tools, though it doesn't state when NOT to use this tool (e.g. cloning an existing grid with wiki_grids_clone).

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