Api evidences partial update

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the description adds nothing about mutation semantics, merge-vs-replace behavior, permissions, or side effects. It is not contradictory with readOnlyHint=false, but for a write endpoint with zero extra disclosure it falls below the minimum-viable bar.

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?

It is a single short sentence, so there is no bloat, but brevity here comes from under-specification rather than discipline. The one sentence present conveys no actionable information.

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?

This is a mutation tool taking an untyped free-form body object, with no output schema and no annotation-level detail about what changes. A description that says only 'viewed or edited' leaves an agent without the information needed to construct a valid call or predict its effect.

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% and the description never mentions the two parameters. The required 'id' and the completely opaque 'body' object (anyOf object/null, additionalProperties true) — the actual payload of a partial update — are left wholly undefined by both schema and prose.

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 sentence is generic Django-REST boilerplate: 'API endpoint that allows evidences to be viewed or edited' names the resource but describes it with the vague verbs 'viewed or edited' rather than the actual PATCH-partial-update behavior. It gives no way to distinguish this tool from the many sibling evidences tools (evidences_update, evidences_retrieve, evidences_list, evidences_partial_update), so it does little more than restate the name.

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?

There is no when-to-use guidance and no mention of alternatives. Saying the endpoint allows evidences to be 'viewed or edited' actively misroutes an agent away from evidences_retrieve for reading and does not explain why one would choose partial update over the full update variant.

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