publer_list_media

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

No annotations provided. The description implies read-only browsing but does not disclose pagination behavior, rate limits, or what data is returned. The mention of a 'page' parameter is present in schema but not explained in the description.

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, minimal verbosity. However, the second sentence includes inaccurate information, which detracts from clarity. Could be improved by omitting false filter claims.

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?

No output schema, so description should explain return values and pagination. It mentions the page parameter but doesn't describe page size or how to iterate. Lacks details on result format and limitations.

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?

Although schema coverage is 100%, the description introduces filters (usage status, source) that are not actual parameters, causing confusion. It does add some value by linking 'search' to name/caption, but misinformation reduces overall quality.

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?

Clearly states the verb (browse) and resource (Publer media library). Mentions filtering capabilities, distinguishing it from sibling tools like publer_list_posts and publer_upload_media_from_url.

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 description claims filters for 'usage status' and 'source' that do not exist in the input schema. While it does list some valid filters, the inclusion of non-existent filters is misleading and provides poor guidance for when to use this tool.

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