marketplace_login

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

With no annotations, the description carries the full burden well: it discloses the visible window, that Claude never types credentials, and that the call blocks until login completes or timeout. It omits what happens on timeout/failure and whether the session persists for later marketplace tools.

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?

Three tight sentences, front-loaded with the core action and credential-handling caveat. Minor redundancy in the trailing 'Optional: search works logged out' note, which is compressed to the point of slight ambiguity.

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?

For a low-complexity, single-parameter tool with no annotations or output schema, the description covers behavior and security posture but not the outcome on failure or whether the authenticated session carries over to sibling tools like marketplace_watch or marketplace_search.

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 single parameter has 0% schema coverage, so the description should compensate. It mentions 'the timeout passes', implying timeout_minutes governs the wait, but gives no units, range, or default, leaving the schema's min/max/default undocumented in prose.

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?

States a specific verb and resource: opening a visible Facebook browser window for manual user login. It is clearly distinct in intent from the search/listing/watch siblings, though it never names an alternative to contrast against explicitly.

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?

Gives clear context for when the tool is needed (hand login by the user) and a useful negative hint that search works logged out, implying this is not always required. It stops short of naming which sibling tools do or do not require a session.

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