TopAIMuza.pl

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds content context (data 'as on the profile', YouTube figures carry a measurement date), but says nothing about failure behavior for an unknown artist. With annotations carrying the behavioral load, a 3 is appropriate.

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?

The purpose is front-loaded in the first clause, which is good. However, the sentence then becomes a long comma-chained enumeration of every returned field, and the bilingual Polish restatement repeats the same content, so much of the text does not earn its place alongside the output schema.

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 one-parameter read tool with a full output schema and complete annotations, the definition covers what is needed to call it correctly and what kind of data comes back. Only the not-found and identifier-ambiguity cases are unaddressed, which is a minor gap at this complexity.

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% and the single parameter's schema description already lists name, slug, and profile URL with an example. The description restates the same three accepted forms without adding format constraints or disambiguation rules, so it meets but does not exceed the baseline.

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 ('Profile of one artist on TopAIMuza.pl') and enumerates the content returned, so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling search_artists, which is the one thing an agent must infer.

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 makes clear that this is a single-artist lookup keyed by name, slug, or profile URL, which implies usage as opposed to the plural search tool. But it never states when to prefer get_artist over search_artists, nor what happens if the identifier is ambiguous or missing.

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

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

The description adds valuable context about the output structure, specifying that each genre listing includes both the number of artist profiles and a direct link to the genre page. This goes beyond the safety assurances provided by the annotations.

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?

The description is highly concise and efficient. It combines the key information—resource, content, and additional metadata—into a single, front-loaded summary.

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?

Given that the tool is parameter-less and includes an output schema, the description provides all necessary context for the AI agent. It fully describes the nature of the data it will receive.

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?

With zero parameters, the description must compensate for missing semantic information. The description fulfills this requirement by detailing the content of the returned list, which would otherwise be opaque without the output schema.

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?

The purpose is extremely clear: it lists the genres available in the specific catalogue (TopAIMuza.pl). By providing examples like 'disco polo, rap, pop, rock', it immediately sets the expected resource type.

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?

Since this tool takes no parameters and serves as a foundational list, its usage is inherently clear for discovery. While it doesn't explicitly state 'use this over X', its purpose as a high-level catalog view makes its intended use obvious.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the catalogue's subject matter and the 25-track ceiling, which is already in the schema, and says nothing about ordering stability, pagination, or empty-result behavior.

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?

The description is short and front-loads the resource and scope before the returned fields. The bilingual duplication roughly doubles length for localization purposes, which is defensible but not maximally tight.

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 an output schema covering return values and annotations covering the safety profile, the description only needs to establish scope and the recency ordering, which it does. Minor gaps around ordering determinism and behavior on unknown genres are low-stakes for a read-only listing tool.

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% and both parameters (genre, limit) are documented in-schema with bounds and defaults. The description restates the genre filter and the 25-item cap without adding syntax, slug-matching, or fallback behavior beyond what the schema already provides.

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 ('newest track pages'), resource (TopAIMuza.pl catalogue of Polish AI music), optional genre scoping, and the fields returned. The 'newest' ordering implicitly separates it from top_ranking and search_tracks, but no sibling is named, so the differentiation is inferred rather than stated.

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 phrase 'optionally within one genre' hints at when to supply the genre parameter, but there is no explicit guidance on when to choose this tool over search_tracks or top_ranking, and no exclusions. Usage is implied rather than specified.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words elsewhere: typo tolerance, the result cap, and the ordering rule when only a genre is supplied. That ordering rule is genuinely useful behavior not derivable from the schema. It stops short of saying what an unfiltered call returns or how partial matches are ranked when both query and genre are given.

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 tight sentences with the core action and the return shape front-loaded, plus one ordering caveat that earns its place. The full bilingual duplication nearly doubles the length for no added information, which costs a point.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety semantics. The remaining gap is the zero-parameter case (all three params are optional) — the description never says whether an empty call returns all artists or fails.

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; the description earns above that by adding fuzzy matching semantics for the name ('typos tolerated') and by clarifying that genre-only queries sort by chart position, which explains how the optional parameters interact.

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 ('Search AI music artists in the TopAIMuza.pl catalogue by name ... and/or genre'), which is immediately actionable. It does not contrast itself with siblings like get_artist or search_tracks, so an agent must infer that this is the list/search variant rather than the detail lookup.

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?

Usage is implied by the phrase 'by name (typos tolerated) and/or genre', which tells the agent the two valid entry modes, but there is no explicit 'use this instead of X' routing, no statement about what happens with zero arguments, and no exclusions.

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

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

Annotations already cover safety: read-only, idempotent, closed-world, non-destructive. The description adds useful behavioral detail: result fields returned (title, artist, release date, links) and a hard cap of 25 tracks. It doesn't explain pagination or empty-result behavior, but the annotations set a lower bar.

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?

The description is two sentences, front-loads the action and scope, and doesn't wander. The bilingual duplication increases length, but it's purposeful for a Polish-language API and doesn't obscure the main point.

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 an output schema present and rich annotations, the description doesn't need to explain return structures. It covers the tool's purpose, the optional artist filter, the result cap, and the returned fields, which is sufficient for correct invocation.

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 all three parameters are fully documented in the schema, including the 1–25 limit range and the default of 10. The description adds only that the artist filter is optional and restricted to one artist; it doesn't contribute much beyond the schema and stays at baseline.

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?

The description gives a specific verb and resource ('Search track pages on TopAIMuza.pl') and narrows scope to title plus an optional single artist filter. That makes it easy to tell apart from search_artists and get_artist without opening any schema.

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 text explains that the artist filter is optional and limited to one artist, which implies the intended usage. It doesn't say when to prefer this tool over search_artists or get_artist, and there are no explicit exclusions or preconditions.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context: the fixed upstream source, the exact fields in a row (place, movement since yesterday, artist, genres, platform figures with read dates, profile link) and the 25-place ceiling.

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?

The purpose and source are front-loaded in the first clause, and every English clause adds information. The full Polish restatement duplicates the same content and costs space without adding guidance, which keeps it short of a 5.

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 an output schema present and annotations covering safety, the description supplies what is still needed: source of truth, row fields, and result ceiling. Only the freshness semantics of 'movement since yesterday' (how often the chart updates) and behavior for an unknown genre slug are left unaddressed.

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%, with both genre and limit fully documented including range and default, so the schema carries the burden. The description only restates the optional genre filter and the 25-place limit without adding syntax, slug examples or fallback behavior beyond the schema.

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 resource (the TopAI chart of Polish AI music on TopAIMuza.pl) and even names the canonical page it mirrors, plus the fields returned. It is unmistakably different from siblings such as get_artist, search_tracks, list_genres and new_releases.

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 optional genre filter and the 25-place cap imply how to scope a query, but nothing states when to pick this over search_tracks or new_releases, nor any exclusion. Usage is only inferable from the purpose statement.

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