create_template_permission

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

Annotations already declare readOnly=false, destructive=true, openWorld=true, and idempotent=false, so the safety profile is covered. The description adds the POST endpoint and a body-encoding caveat, but does not explain the access-control impact, required authorization, or non-idempotent effects of adding a permission.

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 short and front-loaded with the action and endpoint. The abbreviation 'Perm' slightly reduces clarity, but there is little wasted text.

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 destructive mutation with a nested body object, three required parameters, 0% schema description coverage, and no output schema, the description is incomplete. It omits body field semantics, access implications, and expected response behavior.

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 description coverage is 0%, so the description must compensate for undocumented parameters, but it only says 'Supply API fields in body' and notes JSON-encoded string fields must remain strings. It does not explain required fields such as role_slug and permissions, or what the permissions integer represents.

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: 'Add Template Perm' plus the POST endpoint for template permissions. It is understandable despite the abbreviation 'Perm', and it distinguishes creation from sibling list/get/delete/update tools, though it does not explicitly contrast with update_template_permission.

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 gives no guidance on when to use this tool versus update_template_permission, delete_template_permission, or list_template_permissions. The only usage information is the HTTP endpoint and a body-format caveat, leaving the agent to infer intent.

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