confluence_listSpaceTemplates

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

Discloses that body is not expanded by default for speed, and that expandBody option makes it slow. No annotations exist, so description carries full burden; this is adequate but could mention authorization or rate limits.

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 sentences, efficiently conveying purpose, usage hint, and key behavioral note. No unnecessary words.

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?

Lacks description of return format, pagination, or error conditions. For a list tool with no output schema, more detail on what is returned would improve completeness.

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% and description adds context: example for spaceKey, nature of nameContains filter, and behavioral effect of expandBody. Adds value beyond 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?

Clearly states 'List space page templates' with specific verb and resource, and includes API endpoint for precision. Distinct from sibling tools which focus on update, move, delete, etc.

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?

Provides specific use case (spaceKey=TempStream for ДРП Create from template) and mentions optional nameContains filter. Does not explicitly exclude alternative tools, but sibling list provides context.

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