Personal Context MCP Server

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 offers no details. It does not address critical aspects like required permissions, whether deletion is permanent or reversible, rate limits, or response format, making it inadequate for a destructive 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?

The description is extremely concise with a single sentence, 'Delete specific personal information', which is front-loaded and wastes no words. However, this brevity contributes to underspecification rather than effective communication.

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, lack of annotations, 0% schema coverage, no output schema, and multiple sibling tools, the description is severely incomplete. It fails to provide necessary context for safe and correct usage, such as behavioral traits, parameter meanings, or differentiation from alternatives.

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%, so the description must compensate but adds no information about the parameters 'category' and 'subcategory'. It does not explain what these parameters represent, their expected values, or how they affect the deletion process, leaving them undocumented.

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 specific personal information' restates the tool name/title with minimal elaboration, making it tautological. While it includes the verb 'delete' and resource 'personal information', it lacks specificity about what constitutes 'personal information' or how deletion occurs, failing to distinguish meaningfully from sibling tools like 'update_personal_info' or 'batch_save_personal_info'.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or comparisons to sibling tools such as 'update_personal_info' or 'list_available_personal_info', leaving the agent without context for selection.

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