direct_delete_feeds

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

With no annotations provided, the description carries the full burden. It discloses the tool is a write operation, but provides no context on consequences, irreversibility, required permissions, or return behavior. The 'allow_write=true' hint is more about a parameter than a behavioral guarantee.

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 concise sentence that front-loads the key operation ('WRITE: feeds.delete by ids') and includes the critical flag 'allow_write=true'. It is efficient, though it omits some important details.

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 mutation tool with no annotations and no output schema, the description is under-specified. It does not disclose what happens on success/failure, whether the delete is permanent, or the role of dry_run. The existing text leaves significant gaps for an agent to safely invoke this tool.

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 only 33%, with only allow_write having a schema description. The tool description mentions 'by ids' but does not explain the dry_run parameter or further elaborate on ids. It adds minimal value beyond the schema for the required parameters.

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 clearly states the operation: 'feeds.delete by ids' with a 'WRITE:' prefix, making it unambiguous that this tool deletes feeds by their IDs. It distinguishes from sibling read tools like direct_list_feeds and other write tools like direct_delete_keywords.

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 implies usage for deleting feeds by IDs, and the 'WRITE:' prefix indicates it is a mutation tool. However, it does not explicitly state when to use this tool instead of alternatives, nor mention exclusions or prerequisites beyond 'allow_write=true'.

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