unlink_concept_from_session

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

No annotations are present, so the description carries the full burden. It only states the action without disclosing behavioral traits like reversibility, side effects, or dependencies. The agent learns nothing about the consequences of the operation.

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 extremely concise at one sentence, but it is too sparse to be helpful. It saves space but sacrifices necessary details. A slightly longer description with key behavioral notes would be more effective.

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?

Despite having an output schema and three parameters (two required), the description fails to mention return values or the effect of the operation beyond removal. It is incomplete for the tool's complexity, leaving the agent without critical context.

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 already describes concept_id and session_id as 'ID of the concept' and 'ID of the session', but the description adds no extra meaning. It does not explain the optional actor_context parameter, which lacks a schema description. With 67% schema coverage, the description should have compensated for the missing documentation.

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 action ('remove') and the resource ('concept reference from a session'), making it distinct from sibling tools like 'link_concept_to_session' or 'unlink_artifact_from_session'. However, it does not explain what a 'concept reference' means, which could be slightly ambiguous.

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 no guidance on when to use this tool versus alternatives such as 'delete_concept' or 'remove_tag_from_concept'. No when-to-use or when-not-to-use information is given.

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