get_extension_info

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

The description explains the basic behavior (retrieving a path) but lacks details about return format, potential errors (e.g., extension not found), or any side effects. Since no annotations are provided, the description carries the full burden for behavioral transparency.

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 two sentences, both directly relevant and devoid of fluff. It efficiently conveys purpose and usage.

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?

The description adequately covers the tool's purpose and usage context but does not specify output format or error conditions. Given the simple nature (no parameters, no output schema), it is minimally complete, but additional detail on return value would improve completeness.

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 are no parameters (0 params), and the schema coverage is 100% (empty schema). Per guidelines, a baseline of 4 is appropriate when no parameters are present, and the description does not need to add parameter semantics.

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 ('Get the absolute local path') and the resource ('unpacked browser extension folder'). It also provides context for usage, distinguishing it from sibling browser automation tools that perform actions rather than retrieve information.

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 explicitly mentions when to use this tool ('to help the user load the extension if it is not connected'), providing clear context. However, it does not discuss alternatives or when not to use it, though given its unique purpose, this is a minor omission.

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