Contract Testing: Create Pacticipant

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

The description contradicts the annotation 'readOnlyHint: true'. The description indicates a write operation ('Register...'), but the annotation suggests the tool is read-only. This is a serious inconsistency that misleads the agent about the tool's side effects. Additionally, the description does not disclose other behavioral traits such as whether the operation is idempotent (annotation says true, but creation typically is not) or what happens if the name already exists.

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 well-structured with a clear title, brief introductory sentence, and a formatted parameter list. It uses a heading for 'Toolset' and lists parameters with types and requirements. It is appropriately sized for the complexity, though it could be slightly more 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 the absence of an output schema and the annotation contradiction, the description lacks important context. It does not describe what the tool returns (e.g., the created pacticipant object), nor does it explain prerequisites or consequences (e.g., what happens if the name already exists). The contradiction undermines 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%, so the baseline is 3. The description lists parameters with brief descriptions that largely mirror the schema. However, it adds useful notes like 'name (cannot be changed after creation)' and categorizes parameters under 'Toolset: Pacticipants'. It does not significantly enhance understanding beyond what the schema provides.

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 clearly states the tool's purpose: 'Register a new application/service (pacticipant) in the workspace.' It specifies what a pacticipant is and that it creates a new entity. The tool name 'create_pacticipant' is reinforced, and it is easily distinguished from siblings like 'get_pacticipant' or 'delete_pacticipant'.

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?

The description does not explicitly state when to use this tool versus alternatives. While the purpose is clear, there is no guidance on prerequisites, context, or when not to use it (e.g., when the pacticipant already exists). The tool's role within the broader workflow is implied but not stated.

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