ff_fetch

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

Describes key behavior: operates from inside logged-in tab with real cookies/auth, requires bridge add-on, and returns status plus body. Lacks details on error handling, rate limits, or behavior when tabId is not provided.

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?

Two concise sentences, no fluff, front-loaded with the primary action. Every part adds value.

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 no output schema or annotations, the description covers the core functionality but lacks details on the options parameter and return format specifics. Adequate for basic understanding but not fully comprehensive.

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%; description explains the url parameter's context but does not detail the optional tabId or options object. Leaves agent to infer meaning from context.

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?

Clearly states the tool calls a URL/API from inside a logged-in tab, returning status and JSON/text body. Differentiates from siblings by emphasizing the authentication context and real browser operation.

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?

Provides context for use ('Great for scraping the site's own API') and prerequisite (needs bridge add-on). However, does not explicitly state when not to use or compare with alternatives.

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