Contract Testing: Patch Pacticipant

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

The description says 'update' which is a write operation, but the annotations set readOnlyHint=true, which contradicts. This is a serious inconsistency. No additional behavioral traits (e.g., error handling, idempotency details) are disclosed.

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 and a parameter list. Front-loaded with the core purpose. 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?

Despite conciseness, the description lacks behavioral context such as return value, error scenarios, or authorization requirements. The annotation contradiction further 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 baseline is 3. The description lists parameters with their descriptions, which mostly mirror the schema. No additional semantic value like examples or constraints are provided.

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 'Partially update a pacticipant's metadata' with the verb 'update' and resource 'pacticipant'. It explicitly mentions partial update, distinguishing it from a full update tool like contract-testing_update_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?

Implies use for partial updates but does not explicitly state when to prefer this over the full update tool. The 'Toolset: Pacticipants' line provides context but no specific guidance on alternatives.

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