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

Annotations already flag destructiveHint=true and idempotentHint=false, and 'Toggle' is consistent with that. The description adds a genuine precondition beyond the annotations: the member's 'Allow my assistant to act' switch must be enabled, which the agent needs to know before calling. It stops short of describing failure behavior when the switch is off or what the response contains.

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 short sentences, zero filler, with the operation and its scope stated before the precondition. Nothing could be removed without losing information.

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 one-parameter toggle whose safety profile is fully covered by annotations, the description supplies the operation, the target scope, and the assistant-permission precondition. It is nearly complete; only the behavior when the precondition is unmet or the return value are unstated, which is minor given the tool's simplicity.

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?

There is one parameter with 100% schema coverage, so the schema already documents 'slug' including its source (search or profile result url). The description's '(by slug)' adds no meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb (toggle), resource (a GigXchange profile in the member's favourites list), and the selector (slug). It is the only favourites-manipulating tool among the siblings, so an agent can route to it unambiguously without opening the schema.

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?

Usage is implied: use it when the member wants to add or remove a profile from their favourites. There is no explicit when-not-to-use guidance and no named alternative, though the sibling list contains no competing favourite tool.

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