Block/Unblock SimpleLogin Alias Contact

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

Adds value beyond annotations: explains that blocking stops mail to/from the contact without deleting the reverse-alias, and that it returns the new block_forward state. No contradiction with idempotentHint annotation.

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?

Two sentences, no unnecessary words. First sentence states action and effect, second states return value. Perfectly concise.

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?

With output schema present and description covering behavior and return state, the description is fully complete for this tool's complexity.

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 covers 50% with only account_id described. Description mentions 'contact' but does not elaborate on contactId parameter. Adequate as contactId is inferred, but missing explicit mapping reduces helpfulness.

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?

Clearly states the tool blocks/unblocks a reverse-alias contact from forwarding. Differentiates from siblings like alias_delete_contact and alias_toggle by specifying it does not delete the reverse-alias. Action verb 'Block or unblock' with specific resource 'reverse-alias contact'.

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?

Implies usage for temporarily stopping forwarding without deletion, but does not explicitly compare to alternatives like alias_delete_contact or alias_toggle. Clear context for when to use this tool among sibling tools.

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