test_cms_connection

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

With no annotations, the description carries the full burden. It usefully discloses the required scope (cms:manage) and that it exercises signed webhook delivery, but it does not say whether a real test webhook is dispatched (a side effect), whether the operation is read-only, or what a failure looks like.

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 short sentences, zero filler, and the core purpose is front-loaded. Every clause earns its place.

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?

An output schema exists, so return values need no explanation here, and the auth requirement plus test scope are covered. Still, for an un-annotated tool that performs outbound verification, the description omits side effects and failure semantics, leaving gaps an agent may care about.

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 is expected to compensate, and it does not mention either parameter. However, both parameters are unambiguous integer identifiers (project_id, connection_id) whose names are self-explanatory in context, so little meaning is lost.

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?

States a specific verb ('Test') plus two concrete resources: CMS credentials and signed webhook delivery. This clearly separates it from the sibling CMS tools (list_cms_connections, create_cms_connection, delete_cms_connection), though it doesn't name any sibling explicitly.

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?

'Requires cms:manage' gives a permission prerequisite, and the verb 'Test' implies it is run after a connection is configured, but there is no explicit when-to-use statement and no exclusions or alternatives named. Usage is implied rather than stated.

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