set_site_permission

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

With no annotations present, the description carries the full behavioral burden and does it well. It discloses temporary lease semantics, the fact that prior settings are restored, safe-mode prompting behavior, lab-mode prompt skipping, and the relevant environment variable condition. This is substantial transparency for a mutating tool.

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 compact and front-loaded with the core action, followed by constraints and behavioral nuance. The lab-mode sentence is dense and uses environment-variable jargon, but every sentence contributes meaningful information with no 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?

Given that there are no annotations, 5 parameters, and no schema descriptions, the description covers the main behavior and constraints well. Still, it omits required parameter semantics and does not connect to sibling tools, so an agent would need external knowledge to invoke it with full confidence.

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?

The input schema has 0% description coverage, so the description must compensate. It adds useful constraints for origin, permission, and duration_seconds, and hints at the 'allow' setting value, but it does not enumerate valid settings for the required 'setting' parameter or explain the purpose of 'session_id'. Partial compensation, not complete.

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 first sentence states a specific operation and resource: temporarily setting an origin-scoped browser site permission. It also narrows scope clearly with a duration range, supported origin schemes, and a list of supported permission types, so an agent can tell this apart from related tools like reset_site_permissions.

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 implies when to use the tool—temporary origin-scoped permission leasing—and explicitly lists unsupported origins and permission categories. However, it never names alternatives like reset_site_permissions or states a clear rule for choosing between them, so the usage guidance remains mostly implicit.

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