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

Annotations already supply destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered; the description's 'Permanently' mostly restates that. The genuinely additive part is the MCP-scope exclusion, but nothing is said about authorization requirements, whether deletion cascades to agent references/attached agents, or whether it is recoverable.

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 short sentences, front-loaded with the action and resource, then the scope caveat. No filler.

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 one-parameter destructive tool with no output schema and annotations already declaring destruction and idempotency, the description covers the essentials. It falls slightly short on cascade/authorization consequences, which matter for an irreversible delete.

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?

The single toolId parameter has 0% schema description coverage, so the description must compensate; saying 'HTTP tool by toolId' clarifies that the ID refers to an HTTP (non-MCP) tool, which is useful but stops short of format, source (e.g., from list_agent_tools), or validation behavior.

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?

A specific verb ('Permanently delete'), specific resource ('Convocore agent HTTP tool'), and a keying parameter ('by toolId') are all stated, and the second sentence carves out the MCP-tool scope so the tool is distinguishable from get_agent_tool, update_agent_tool, delete_agent, and delete_agent_variable.

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 negative scope ('Does not delete MCP tools') implies when not to use it, but there is no explicit guidance on when to prefer this over update_agent_tool, get_agent_tool, or list_agent_tools, and no preconditions such as confirming the toolId first or obtaining prior authorization.

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