post_routers_configs_tls

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

Annotations declare readOnlyHint=false and destructiveHint=false, consistent with a create operation. Description adds behavioral context: TLS configs are identified by their base64-encoded certificate string, which must be unique on the account. No contradictions.

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?

Two sentences front-loaded with purpose and permission. Includes endpoint URL for context. Slightly verbose with HTML line break, but otherwise concise.

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 2 required parameters and no output schema, the description adequately covers creation purpose, uniqueness constraint, and permission. Could mention return value or side effects, but overall complete for the tool's simplicity.

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 covers both parameters with descriptions. Description adds semantic value by specifying that the key must match the certificate's public key and that the certificate alone can be used (though both are required per schema). This clarifies the relationship between parameters.

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 'Create TLS config' and explains its purpose: allowing a certificate and key to be used in router configs. It differentiates from sibling tools like get_routers_configs_tls (read) and delete_routers_configs_tls (delete) as a create operation.

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 required permission ('Device command and configuration, Edit') and describes the use case where specifying only the certificate automatically adds the matching key. Does not explicitly state when not to use, but context is clear.

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