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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value the annotations do not: merge semantics ('only fields to change'), which tells the agent that omitted fields are preserved rather than wiped. It stops short of saying what can be destroyed or whether permissions are required, which matters for a destructive mutation.

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 sentences, no filler, with the identity/scope first and the critical partial-update instruction second. 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?

For a destructive mutation with a fully undocumented nested object and no output schema, the description should at minimum list the patchable tool fields or point at get_agent_tool as the way to discover them. Annotations cover safety, but the payload contract is the biggest remaining gap and it is unaddressed.

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 nested `tool` object declares no properties at all, so the schema carries no semantics. The description explains the merge behavior of `tool{}` but never enumerates which fields are valid inside it, leaving the agent to guess the payload shape for the one parameter that matters.

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 (patch) and a specific resource (existing Convocore agent HTTP tool) plus the identifier used to address it. Among the agent_tool siblings (create/delete/get/list/test), the patch verb reasonably separates it, though the description never names the sibling it is distinct from.

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?

'Pass only fields to change inside tool{}' gives clear partial-update guidance, which is genuinely useful. But there is no statement of when to prefer this over create_agent_tool or delete_agent_tool, no prerequisites, and no failure conditions (e.g. what happens if toolId doesn't exist).

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