marketplace_info

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

With no annotations, the description must carry the burden. It states what the tool returns (overview, stats, links) but does not disclose whether it performs network calls, returns cached data, or any limitations. For a read-only info tool, the behavior is reasonably transparent, but some details are absent.

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 sentence that is dense and front-loaded with the primary purpose ('Platform overview'). No filler or repetition. Every phrase adds value.

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 zero-parameter, no-output-schema tool, the description is nearly complete. It names the content (overview, stats, links) but could specify what 'current stats' refers to or whether links are URLs or internal references. Minor gap, but not critical for 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?

The tool has zero parameters, so there is nothing to clarify. The baseline for no parameters is 4, and the description adds no unnecessary parameter information, which is appropriate.

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 tool provides a platform overview covering what 123skills is, current stats, and links to key documents. This is a specific verb+resource (overview) and naturally distinguishes itself from siblings like my_profile (personal info) or list_skills (skills list).

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 intended use case is implied: invoke this to learn about the platform, stats, or find links. However, it doesn't explicitly state when to use it vs. alternatives, nor does it mention any exclusions or prerequisites. Adequate for a simple info tool, but lacking explicit routing.

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