linkedin_forget_answer

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the destructive nature is known. The description adds the rationale for deletion (wrong answer) but does not disclose irreversibility or the confirm requirement, which is instead covered by the schema parameter description. No contradiction with annotations.

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, front-loaded sentence that immediately states the action and resource, with an illustrative example. Every word earns its place; 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?

This is a simple destructive tool with strong annotations and full schema coverage. The description covers the purpose and typical use case well. The only minor gap is not explicitly stating the confirm requirement, but that is fully handled by the schema and the tool remains clear enough for an agent.

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 100%; both 'confirm' and 'question' have detailed descriptions including irreversibility and loose matching. The tool description adds no additional parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 uses a specific verb 'Delete' with a clear resource ('a remembered screening-question answer') and includes a concrete example ('after it turns out to be wrong'). It clearly distinguishes this tool from siblings like add/delete profile sections or skills.

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 clear context for when to use the tool ('after it turns out to be wrong'), implying a corrective workflow. However, it does not explicitly mention alternatives (e.g., linkedin_get_remembered_answers for viewing) or state 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.