djd-agent-score-mcp

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

Adds critical cost information ('FREE') not present in annotations. Aligns well with annotations (idempotentHint=true supports safe re-registration). Could explicitly mention behavior on duplicate wallet registration.

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?

Well-structured with front-loaded purpose. Includes Args section (redundant with schema) but necessary to document Returns shape since no output schema exists. 'FREE' is high-value early information.

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?

Good coverage given idempotent/destructive annotations and described return shape {success, message}. Addresses cost and safety profile. Minor gap: doesn't clarify if registration is required before using scoring siblings.

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 coverage is 100%, so baseline applies. Description frames parameters as 'metadata' which adds conceptual grouping, but the Args section largely repeats schema descriptions without adding syntax details or examples beyond the schema.

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?

Clear specific verb ('Register'), resource ('AI agent wallet'), and scope ('with metadata'). Distinct from scoring/checking siblings (score_basic, check_blacklist, etc.) as a setup/onboarding operation.

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?

Provides cost context ('FREE endpoint') but lacks explicit workflow guidance (e.g., 'use this before score_basic') or prerequisites. No mention of when NOT to use or alternatives to registration.

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