cipp_create_standard_template

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

Description goes beyond annotations by warning of high impact and tenant modification on next standards run, while annotations only indicate non-readonly and non-destructive. No contradiction. Provides critical behavioral 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?

Extremely concise: one sentence with key warning, action, and instruction, all front-loaded. 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?

Given no output schema, description covers purpose, impact, and user confirmation, but lacks details on return value or error states. Still fairly complete for a mutation tool with side effects.

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 already provides 100% coverage for the single parameter 'template' with a description that includes the requirement for 'tenantFilter'. Description adds minimal extra meaning 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?

Description clearly states 'Creates or updates' a 'CIPP Standards Template' (upsert by GUID), distinguishing it clearly from sibling tools that list, delete, or check standards.

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?

Explicitly instructs to 'Confirm with the user before invoking' and warns about high impact, but does not specify when not to use or mention alternative tools for read-only operations.

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