preview_new_page

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

Annotations already indicate a non-read, non-destructive side effect, and the description adds that the tool only previews and does not change Cosense. This is useful behavioral context. It could still mention what the preview output looks like, but the non-mutating preview behavior is clearly conveyed.

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, all informative and front-loaded with the core purpose. There is no redundant repetition of schema fields; every sentence contributes meaning.

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?

Given the output schema exists, the return format does not need explanation. The description covers what the tool does, when to use it, and the meaning of the inputs. A small gap is not naming the sibling preview_edit or submit_edit for the actual write, but the guidance is otherwise sufficient.

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 0%, so the description must carry meaning for parameters. It explains that 'title' and each item in 'lines' represent one Cosense line, which adds real semantic value beyond the raw schema. project_url remains implicit, but it is reasonably inferable from the tool's purpose.

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 states a specific verb and resource ('Preview creation of a new page'), and clarifies it does not change Cosense. It is distinguishable from siblings like preview_edit because it mentions creating a new page, though it does not name the sibling explicitly.

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 says to use this only for an explicitly requested write, giving a clear condition. It could be improved by explicitly naming preview_edit or submit_edit as the actual-write alternative, but the usage context is clear enough.

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