confluence_syncPageToSpaceTemplate

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

With no annotations, the description must fully disclose behavior. It mentions copying body.storage but does not clarify whether it creates or updates a template, what happens to other fields, or if the operation is destructive. The term 'Create from template snapshot' is ambiguous.

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 one sentence plus an example, front-loading the key action. It is efficient, though it uses domain-specific acronyms (BSA, TempStream) that may reduce clarity for some users.

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, so the description should hint at return values or error conditions. It does not. The tool has 6 parameters but only 2 are required; the purpose of optional parameters like name, description, descriptionSuffix is not explained.

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 parameters are documented. The description adds a helpful example but does not elaborate on parameter meaning beyond the schema. Baseline score of 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?

The description clearly states the verb 'copy' and the resource 'body.storage from a BSA/page contentId into a TempStream space template'. It provides a concrete example with specific IDs, making the purpose unambiguous and distinct from sibling tools like create/update from file or list templates.

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 implies a 'fast path' use case but does not explicitly state when to use this tool versus alternatives like createSpaceTemplateFromFile or updateSpaceTemplateFromFile. No when-not-to-use guidance is provided.

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