panelica_spam_post_v1_spam_blacklist

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

The description explicitly discloses the required OAuth scope (`email:write`) and states that the operation mutates server state, which goes beyond the annotations' readOnlyHint=false. This gives the agent important auth and side-effect context, though it does not describe duplicate-entry behavior or return payload.

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 compact and front-loaded: action first, then HTTP method/path, category, required scope, and mutation flag. Every line carries useful operational information and there is no filler.

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?

The description is too incomplete to support a correct invocation: the request body is completely undocumented, no example is provided, and no alternative/usage guidance is given. An agent would likely need external API documentation to construct the request, which undermines the purpose of the tool description.

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 schema's only parameter is a free-form body whose description explicitly says the schema is not statically declared, and the tool description adds no field names, shape, or example payload. Despite the nominal 100% schema coverage signal, actual semantic coverage is near zero: an agent still does not know what fields to send to add an address to the blacklist.

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 names the operation ('Add to blacklist') and gives the exact HTTP endpoint, category, and required scope, so an agent can identify the resource being affected. It does not explicitly contrast it with the sibling spam whitelist tool, but the blacklist resource is unambiguous from the endpoint and category.

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 given about when to choose this tool over alternatives such as panelica_spam_post_v1_spam_whitelist or panelica_spam_delete_v1_spam_blacklist_id. The description implies 'when you want to blacklist something' but provides no context, prerequisites, or exclusion criteria.

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