delete_question_option
Delete a question option to manage your feedback questionary.
Instructions
Remove an option.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Delete a question option to manage your feedback questionary.
Remove an option.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a destructive action (removing an option), but it lacks details on side effects, reversibility, or permission requirements. Since annotations are absent, this minimal disclosure leaves the agent with significant uncertainty.
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 a single short sentence, which is concise. However, it is arguably too brief and lacks necessary information, but it does not contain filler or redundancy.
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 deletes an option without any defined parameters or output schema, the description is severely incomplete. It fails to explain how the target option is specified, what the expected input is, or what happens after deletion. This is inadequate for safe invocation.
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 zero defined properties and allows additional properties, but the description does not clarify how to specify which option to delete. With 100% schema coverage due to no parameters, the description should have explained the identification mechanism, but it remains silent.
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 'Remove an option' clearly states the verb 'Remove' and the resource 'option', making the tool's purpose apparent. Although brief, it distinguishes from sibling tools like 'delete_question' which deletes a question, so purpose is clear.
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?
No guidance is provided on when to use this tool versus alternatives, such as when to delete a question option rather than a question itself. There is no mention of prerequisites, conditions, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/skippedaga/yanifend-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server