codivupload-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Create Post' implies a write/mutation operation but provides no information about authentication requirements, rate limits, side effects, what happens on success/failure, or any behavioral characteristics. The description doesn't even indicate whether this is a simple or complex operation.

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?

While technically concise with only two words, this is an example of harmful under-specification rather than effective conciseness. The description fails to provide any meaningful information that would help an AI agent understand or use the tool. Every word should earn its place, but here the words don't provide sufficient value beyond the tool name itself.

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?

Given that this is a mutation tool (implied by 'Create') with no annotations, no output schema, and multiple sibling tools including other creation operations, the description is completely inadequate. It doesn't explain what gets created, where, with what defaults, or what the result looks like. For a tool that presumably creates content in some system, this minimal description leaves critical gaps in understanding.

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 tool has zero parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain any parameters, and it doesn't contradict the empty schema. Given the zero-parameter situation, a baseline of 4 is appropriate since there's no parameter information to provide beyond what the schema already indicates.

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 'Create Post' is a tautology that merely restates the tool name without adding any meaningful context. It doesn't specify what type of post is being created, what platform it's for, or what resources are involved. While it does contain a verb ('Create') and resource ('Post'), it lacks the specificity needed to distinguish it from sibling tools like 'updatepost' or 'deletepost' beyond the obvious action difference.

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 description provides absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this operation is appropriate, or what distinguishes it from similar tools like 'updatepost' or sibling creation tools like 'createwebhook' and 'createyoutubebroadcast'. The agent receives no contextual information about appropriate use cases.

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