details_patch

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

Description states only provided fields change, implying non-destructive partial update. No annotations are present, so the description carries the full burden. It adequately conveys basic behavior but omits details like merging vs replacement.

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?

Single sentence with no redundancy. Every word contributes to the meaning. Front-loaded with 'Partial update'.

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?

With 6 parameters, no output schema, and no annotations, the description is too sparse. It lacks context on what 'details' resource is, return values, and any constraints for the mutable fields.

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 33% but the description adds no parameter-specific meaning beyond the patch concept. Missing descriptions for 4 of 6 parameters are not compensated.

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 'Partial update' for the details resource. It differentiates from 'details_update' (full update) by emphasizing only provided fields change. Verb+resource is specific, but could be more explicit about what 'details' refers to.

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?

No guidance on when to use this tool vs alternatives like 'details_update'. The description implies partial update use case but does not specify prerequisites or scenarios.

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