agentlux_browse

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

No annotations provided. Description mentions pagination and USDC pricing, but does not disclose side effects, authentication requirements, or rate limits. It is read-only, but description does not explicitly state that. Minimal behavioral context beyond schema.

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 sentences, front-loaded with the main action, and no wasted words. Every sentence is informative.

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?

Despite no output schema and 5 optional parameters, description omits enum values for category, default for page, and the meaning of search. It inaccurately mentions 'tags', missing important parameter details for effective use.

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 covers 100% of parameters, but description introduces 'tags' which is not a schema property, and mentions 'price range' while only priceMax exists. This inaccuracy could mislead the agent. Adds marginal value but with errors.

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?

Description clearly states the tool browses the AgentLux marketplace for avatar items, with filtering and pagination. It uses specific verb 'Browse' and resource 'marketplace for avatar items', distinguishing it from sibling tools like agentlux_achievements or agentlux_purchase.

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?

Description implies usage for browsing and filtering marketplace items, but no explicit guidance on when to use this tool versus alternatives like agentlux_trending or agentlux_inventory. No 'when-not' or alternative references.

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