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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description usefully adds that the data comes from a live Scan-API catalogue and enumerates the returned fields, though it omits pagination semantics and rate/behavior caveats.

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?

Purpose is front-loaded in the first sentence, followed by capability, scope, and use cases. It is efficiently sized, though the parenthetical "(when known)" is slightly vague and the final returns list is a bit thrown-together.

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, the description compensates by listing the returned fields (name, provider/app_id, category, last_activity, url). Combined with annotation coverage and a fully described input schema, it is complete enough to call correctly, with only pagination/ordering behavior left implicit.

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 the schema already documents sort, limit, and category including defaults and the case-insensitive substring match. The description only reiterates "filter by category" and "choose ordering," adding negligible meaning beyond the schema, so baseline 3 applies.

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+resource (List Canton Network Featured Apps) and mentions the source (live Scan-API-sourced catalogue) and the Canton-specific scope. However it does not differentiate itself from close siblings like list_ecosystem_projects or find_apps_by_pattern, so an agent must infer the distinction from the name alone.

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 concrete usage triggers — "what dApps are live on Canton?" and "discover providers offering a particular service" — which is real context beyond the name. It stops short of naming alternatives or stating when NOT to use it versus sibling listing/search tools.

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