codivupload-mcp

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

No annotations are provided, so the description carries full burden. 'Delete' implies a destructive mutation, but it doesn't disclose critical behaviors: whether deletion is permanent or reversible, what permissions are required, if there are side effects (e.g., cascading deletions), or rate limits. The description adds minimal value beyond the obvious implication of deletion.

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 concise with two words, the description is under-specified rather than efficiently structured. It lacks front-loaded critical information (e.g., what resource is affected, behavioral notes). The brevity comes at the cost of clarity, making it ineffective.

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 the tool's destructive nature, no annotations, and no output schema, the description is incomplete. It should explain the deletion's impact, return values, or error conditions. Sibling tools suggest a profile management context, but the description doesn't leverage this for completeness.

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 input schema has 100% description coverage, with the single parameter 'id' documented as 'The UUID of the profile to immediately delete'. The description doesn't add any parameter details, but with high schema coverage and only one parameter, the baseline is 4. No compensation is needed.

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 'Delete Profile' restates the tool name 'delete_agency_profiles_id' in a tautological manner. It doesn't specify what type of profile (agency profile) or provide any distinguishing context from sibling tools like 'delete_agency_media_id' or 'deletepost'. The purpose is vague beyond the basic verb.

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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing profile ID), exclusions, or relationships with sibling tools like 'get_agency_profiles' for listing profiles or 'post_agency_profiles' for creation. The description provides zero usage context.

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