Conduit

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

No annotations are provided, so the description carries full burden. It discloses the tool performs multiple mutation operations (create, delete, rename, set) and returns an array of results, which is useful behavioral context. However, it doesn't mention permission requirements, error handling, or what 'set current page' specifically means in this context.

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?

The description is perfectly concise with two sentences that each earn their place: the first states all operations, the second describes the return format. No wasted words, front-loaded with the core functionality.

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 multi-operation mutation tool with no annotations and no output schema, the description provides basic operational scope and return format. However, it lacks details about authentication needs, error conditions, batch operation specifics, or what 'result objects' contain. Given the complexity of supporting four different operations, more context would be helpful.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could theoretically mention that operations are specified elsewhere (e.g., in request body) but isn't required given the empty schema.

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 clearly states the tool's purpose with specific verbs (create, delete, rename, set) and resource (page), including batch operations. It distinguishes from siblings like 'duplicate_page' or 'get_page' by covering multiple operations. However, it doesn't explicitly differentiate from all sibling tools that might handle page operations.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'duplicate_page', 'get_page', and 'get_doc_pages', there's no indication of when this multi-operation tool is preferred over more specific single-operation tools or how it relates to other page-related operations.

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