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

With readOnlyHint=true and openWorldHint=false already declaring the safety profile, the description still adds real behavioral context: this is a public directory listing, and each result carries a page_url intended for a human to open in a browser. That human-in-the-loop detail is not recoverable from the annotations. It says nothing about pagination or result volume, which keeps it from a 5.

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 short sentences, front-loaded with the core purpose, and each subsequent sentence carries distinct load: usage guidance then a return-value detail. No filler or restated metadata.

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 no-required-parameter, read-only browse tool with no output schema, the description covers purpose, when to use it, and the one output field an agent needs to act on. Pagination via cursor is only implied in the schema, and there is no sense of directory size or ordering defaults, but nothing critical is missing.

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 description coverage is 100%, so all six parameters (tag, sort, limit, owner, query, cursor) are already fully documented, and the enum/defaults are given there. The description adds no syntax, format, or combination guidance beyond what the schema states, so the baseline of 3 is correct.

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 (browse) and resource (the public directory of charms/apps), and the parenthetical gloss of "charms" as small web apps is genuinely clarifying for an agent unfamiliar with the domain term. It implicitly distinguishes itself from single-item siblings like get_app, but never names an alternative, so it stops short of the top score.

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?

"Use this before building something new, or to find an app to show your human" gives two concrete triggering contexts, which is well above the common 'no guidance' baseline. However, it offers no exclusions or pointers to siblings (e.g. get_app for a single known app, remix_app for reusing one), leaving the selection boundary implicit.

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