agent.marketplace.register

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

With no annotations, the description carries full burden. It mentions idempotency and uniqueness per pubkey, but lacks details on mutation behavior, required permissions, error handling, or return values. Significant gaps for a registration tool.

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 sentences are concise and front-loaded, but the terse style leaves out critical information. It is efficient but could include more detail without becoming verbose.

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 lack of annotations, output schema, and the complexity of 9 parameters with nested objects, the description is far from complete. It doesn't explain what the registration does, success/failure behavior, or prerequisites, leaving major gaps for an agent.

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 input schema has 9 parameters (3 required) with 0% schema description coverage. The description adds no explanation for any parameter, such as the meaning of 'metadata', 'payTo', 'capabilities', or 'status' enum values. This forces the agent to guess parameter semantics.

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 action (register/update) and the target (calling agent in agent-to-agent marketplace). It adds specificity with 'one listing per pubkey' and 'idempotent', distinguishing it from siblings like discover, profile, and review.

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 this tool is for registering or updating your own agent listing, but does not explicitly state when to use it vs alternatives like discover or profile. No exclusions or alternative tool names are mentioned, though context provides sibling names.

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