navvi_persona

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 that personas map to Docker volumes and store config, but does not detail mutation effects (e.g., irreversible deletion), auth requirements, or rate limits. Some behavioral context is present but not exhaustive.

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 well-structured with a clear hierarchy of actions and examples. It front-loads the purpose and uses bullet-like formatting. Each section adds value, though the inclusion of raw code examples could be slightly streamlined.

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?

Given the presence of an output schema (context signal), the description does not need to detail return values. It covers persona creation, retrieval, update, deletion, and mentions resource URLs for state access. It handles the complexity of 9 parameters reasonably well, though error handling is omitted.

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 0%, so the description must compensate. It explains the 'profile' parameter and shows usage patterns via examples, but does not define allowable values for parameters like 'stealth', 'locale', or 'timezone'. Some parameters remain ambiguous.

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 it manages browser personas with specific CRUD operations (create, get, update, list, delete). Examples for each action make the purpose unambiguous and distinguish it from sibling tools like navvi_account or navvi_browse.

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 examples for each action, showing when to use which combination of parameters. It also explains the role of the 'profile' field in tone injection. However, it does not explicitly state when not to use this tool or compare it to alternatives.

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