avito_switch_profile

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

No annotations are provided, so the description carries the full burden. It discloses the two visible effects (account switch + cabinet opened), but says nothing about whether the switch persists across other tool calls, what happens to concurrent state, or what occurs on an invalid index. Useful but incomplete for a state-changing 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?

One sentence, front-loaded with the action and resource, with the parameter's meaning and source tucked into a parenthetical. Zero 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?

For a one-parameter, no-annotation, no-output-schema tool, the description covers the essentials (what it does, how to obtain the index). It omits error/out-of-range behavior and whether the account switch affects subsequent tool calls, which matters for an agent operating a browser session.

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 coverage is 0% and the single 'index' parameter is undocumented in the schema, so the description must compensate — and it does, defining the index as the profile number from avito_profiles with 1 meaning the current profile. It does not state valid bounds or behavior for out-of-range values, so not a 5.

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?

States a specific verb+resource ('switches account to profile ... and opens its cabinet') and ties the operand to a sibling tool, avito_profiles, so it is distinguishable from navigation siblings like avito_open. It stops short of 5 only because the effect on the session vs. just the view is not fully disambiguated.

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 by stating the index comes from avito_profiles and that 1 is the current profile, which tells the agent where to source the value. It never says when this tool should be preferred over simply opening a page, nor any preconditions or when not to call it.

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