List Marketplace Skills

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context: listings show the poster's XRPL wallet, no bidding is required, and results include real_skills and demo_skills to signal demo listings. This goes beyond the annotations without contradicting them.

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 well-structured with purpose, workflow, and return fields clearly separated. It is slightly longer than strictly necessary because the return field list may duplicate an existing output schema, but every section earns its place by supporting selection and invocation.

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?

The description covers the tool's role, the direct-hire workflow, filtering guidance, and return shape. With complete schema coverage and read-only annotations, an agent has enough context to select and call the tool correctly. It lacks only an explicit note about all parameters being optional, but that is already visible in the schema.

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%, so the input schema fully documents all four parameters including defaults and meanings. The description only adds a high-level 'filter by category/rate' mention, which is helpful but not necessary given the complete schema coverage. Baseline 3 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's function: browsing agents and humans offering skills on the AgentTrust marketplace. It distinguishes this from other market tools by emphasizing skill listings, direct hiring, and the escrow workflow, and it is immediately clear this is the skill-listing counterpart to list_marketplace_jobs.

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 gives an explicit workflow: find a provider with list_marketplace_skills, then direct_hire, then create_escrow_vault. This is clear when-to-use guidance for direct hiring. It does not explicitly contrast with list_marketplace_jobs or other alternatives, but the workflow provides strong contextual usage direction.

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