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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds substantial context beyond that: nothing is published until human approval, the maker reviews and submits personally, listing is free, and a link is returned. It does not address repeat invocations (idempotentHint=false) or failure modes, which keeps it at 4.

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?

Four short sentences: audience and action first, then what happens to the link, then the approval/free constraints, then the input rule. Zero filler and the most decision-relevant facts are front-loaded.

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, the description says exactly what is returned ('a private link') and what the caller must do with it. With all 12 parameters documented in the schema and the side-effect/approval flow explained, an agent has everything needed to call this correctly.

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 100%, so the baseline is 3, but the description adds real guidance the schema cannot: 'Pass only what the maker said; leave out what you don't know (the website fills the gaps).' That tells the agent to omit rather than fabricate fields, which is a meaningful semantic instruction for all 12 parameters.

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 ('fills in AppFinder's submission form... returns a private link') plus the audience ('for a maker who wants to list their own app'). This is clearly distinguishable from every sibling, which are all read/search tools (search_apps, get_app, recommend_apps, check_listing).

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?

The opening clause gives the triggering condition ('For a maker who wants to list their own app'), which is enough to select this over the search/discovery siblings. It does not name an explicit alternative or when-not-to-use case, so it falls short of a 5.

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