get_skills

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read and evolving content. The description adds value by specifying the output is a manifest of 44 skills with topics and links to gov.pl, providing behavioral context beyond annotations without contradiction.

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 concise, listing topics in a single sentence. It is front-loaded with the main action 'Manifest 44...' and is efficient, though the list could be slightly more structured.

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, but the description sufficiently explains what the tool returns: a list of 44 bilingual skills with specific topics and links. This is complete for the tool's intended purpose.

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?

No parameters, so schema description coverage is 100%. The description adds no param info (unnecessary), baseline of 4 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?

The description clearly states it manifests 44 bilingual skills from Poland-Vault, listing specific topics and noting links. The verb 'Manifest' is slightly ambiguous but overall purpose is clear. It distinguishes itself from sibling tools like get_budzet or get_dlug, which are more specific, implying this is a broad 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?

No explicit guidance on when to use this tool versus alternatives. The context of sibling tools suggests but does not state that this tool provides an overview, while others like get_budzet or search_poslowie are for specific items. The description lacks 'when-not' or alternative references.

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