browser_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails entirely to mention any side effects, permissions, or operational details. The agent cannot infer whether this tool mutates state, reads data, or requires specific conditions.

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 under-specified to the point of being practically empty. It is not a case of efficient conciseness but of critical information missing. There is no structure or front-loading of any useful detail.

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?

With two parameters, no output schema, and no annotations, the description is drastically incomplete. An agent has no idea what actions are possible, what the effects are, or what the return values might be. This is a profoundly inadequate definition for a tool that likely handles multiple profile operations.

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?

Although the input schema has 100% coverage with descriptions like 'Profile name' and 'Profile action', these are themselves largely uninformative. The description adds no clarification on what constitutes a valid action or how the parameter semantics relate to the tool's operation. It fails to compensate for the schema's vagueness, providing no additional meaning.

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 'Chrome profiles' is a noun phrase that merely restates the tool name without any verb or resource specification. It does not indicate what actions can be performed or what the tool's purpose is precisely, and it does nothing to distinguish it from the many sibling browser tools.

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?

There is no guidance on when to use this tool versus alternatives like browser_session or browser_tab. The description provides no context, prerequisites, or exclusion criteria, leaving the agent entirely without direction on appropriate usage.

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