aiworkers_skill

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

With no annotations, the description fully conveys the read-only nature ('Return'), the non-requirement of an existing key (authentication context), and the informational output. It does not disclose potential response format or size limits, but the presence of an output schema mitigates the need for more detail.

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?

A single, front-loaded sentence that conveys purpose, content, and a key constraint with no wasted words. Every piece of information earns its place.

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 the low complexity (no parameters, simple output), the description adequately covers what the tool does and the key precondition. The existence of an output schema means return value details are not needed here. Minor gap: it could clarify that the output is Markdown text.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter details, but none are needed since the schema is empty and fully covered. The description does not detract from 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?

The description clearly states the verb 'Return' and the resource 'SKILL.md', and specifies the content type ('how to log in and which tools to call'). It distinguishes itself from the sibling 'aiworkers_skill_update' by implying this is a read-only retrieval. The condition 'No existing key required' further clarifies the tool's scope.

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 implies usage for initial onboarding ('how to log in') and signals that no key is required, but it does not explicitly state when to prefer this tool over alternatives like 'aiworkers_login_link' or 'aiworkers_whoami'. No exclusions or when-not-to-use guidance is given.

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