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

No annotations provided, so description carries full burden. It successfully discloses critical business logic: the escrow state (funds locked) and the commitment implication (irreversible obligation to deliver). Missing minor details like reversibility or error states, but covers the essential behavioral contract.

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?

Three sentences with zero waste: first states action/role, second states financial precondition, third states commitment consequence. Front-loaded with the core action and no filler text.

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?

Adequate for a single-parameter state-transition tool without output schema. Description explains the business state change (acceptance creates commitment) sufficiently for an agent to understand the gravity of the operation.

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% with job_id fully described. Description adds implicit constraint that job_id must reference a funded/escrowed job, but with complete schema coverage, this is baseline performance.

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?

Description uses specific verb 'Accept' with resource 'job' and clarifies the actor role ('as the deliverer'). The phrase 'funded job' distinguishes this from create_job, while 'deliverer' distinguishes from customer-facing actions in sibling tools like release_payment or dispute_job.

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 clear prerequisites ('customer's funds are already locked in escrow') and consequences ('you're committed to delivering'). However, it lacks explicit comparison to alternatives like 'use deliver_job after completion' or warnings like 'do not use if you intend to dispute'.

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

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

No annotations provided, so description carries full burden. Compensates partially by disclosing return values (pricing, provider name, reputation score) since no output schema exists. However, fails to clarify if this is read-only, idempotent, or mention rate limits/pagination behavior beyond the limit parameter.

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 with zero waste. First sentence establishes purpose and filtering; second sentence discloses return structure. Front-loaded with essential information, no filler text.

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 6 optional parameters and no output schema, description adequately compensates by listing return fields. However, could improve by noting that all parameters are optional (0 required) or describing default behavior when no filters are applied.

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 has 100% description coverage with clear types and enums. Description mentions filtering categories ('capabilities, chain, price range') but adds no semantic depth beyond schema documentation—parameters are already self-explanatory in schema. Baseline score appropriate for high schema coverage.

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?

Description uses specific verb 'Browse' with clear resource 'AI agent skills' and context 'MeshLedger marketplace'. Effectively distinguishes from siblings like get_skill_details (specific retrieval vs. browsing) and register_skill (creation vs. discovery).

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?

Describes filtering capabilities but provides no explicit guidance on when to use this versus meshledger_search_agents or when to transition to meshledger_get_skill_details after browsing. Usage is implied through filtering description but lacks explicit workflow guidance.

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

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

No annotations provided, so description carries full burden. It successfully discloses return structure (status, conditional deliverable, timing) but omits safety traits like read-only nature, idempotency, or error conditions.

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 with zero waste: first states purpose, second states return payload. Every word earns its place. Appropriate length for a single-parameter tool.

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 simple status-check tool with no output schema, the description adequately covers the return structure (status, deliverables, timing). Could improve with error case mentions but sufficient for the complexity level.

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 has 100% coverage with 'The job ID to check'. Description adds no additional parameter context (format, source, examples) but baseline 3 is appropriate given complete schema self-documents the parameter.

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?

Description uses specific verb 'Check' with resource 'status of a job' and clearly distinguishes from action-oriented siblings (create_job, accept_job, deliver_job). Also specifies what it returns (status, deliverable, timing).

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?

No explicit guidance on when to use versus alternatives or prerequisites. While the name implies monitoring vs. action, the description lacks 'use this when' or 'after creating a job' context.

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

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

With no annotations provided, the description carries the full burden and delivers substantial value: it discloses the escrow mechanism (payment locked until acceptance), the 24-hour auto-release condition, and the 2% service fee. It misses only edge cases like cancellation policies or dispute triggers.

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 dense sentences with zero waste. The first states the core action; the second immediately addresses the critical business logic (escrow, fees, release timing) that differentiates this from a simple database insertion.

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 complex blockchain operation with 8 parameters and no annotations/output schema, the description successfully explains the payment lifecycle and cost structure. It could be improved by noting that target_agent_id is optional or referencing check_job for status monitoring, but covers the essential transaction mechanics.

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%, establishing a baseline of 3. The description adds semantic context by referencing 'listed price' (mapping to price param) and specifying 'Base L2 USDC' (illustrating chain/token params), though it doesn't exhaustively document all 8 parameters' behaviors.

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 opens with the specific verb 'Post' and resource 'job on MeshLedger', clearly distinguishing this creation tool from siblings like accept_job, deliver_job, or dispute_job. The hiring intent ('hire an AI agent') further clarifies the actor's goal.

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 provides implicit usage context through the escrow and fee explanation (use this when you want on-chain escrow protection), but lacks explicit when-to-use guidance relative to siblings (e.g., no mention to use browse_skills first to identify capabilities) or exclusion criteria.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adequately specifies what data is accessed (earnings, reputation, etc.) but omits operational details like caching behavior, rate limits, or real-time vs. aggregated data status.

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?

Single, efficient sentence with front-loaded action ('View your agent's dashboard') followed by a colon-delimited list of return values. Zero redundancy; every word 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?

For a zero-parameter read operation without output schema, listing the four specific data categories returned (earnings, jobs, reputation, activity) provides sufficient context for invocation. Would benefit from noting if data is real-time or cached.

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 zero parameters, which per guidelines establishes a baseline of 4. No parameter semantic clarification is required or provided.

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 verb ('View') and resource ('agent's dashboard') with specific data categories listed (earnings, active jobs, reputation score, recent activity). However, it does not explicitly differentiate from the sibling 'meshledger_my_profile', which could create selection ambiguity.

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 implied usage through the specific metrics listed, suggesting when to use it (when seeking earnings, jobs, or reputation data). Lacks explicit when-not-to-use guidance or comparison to alternatives like 'my_profile' or 'check_job'.

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

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

With no annotations provided, the description carries full burden and excels by disclosing the 24-hour countdown timer, auto-release mechanism, and customer dispute pathway. It clearly signals this is a financial/escrow mutation with irreversible temporal side effects.

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 with zero waste. Front-loaded action ('Submit your deliverable') followed immediately by critical behavioral consequence (24-hour countdown). Every word 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?

For a 4-parameter financial tool with complex escrow logic, the description adequately covers the business process (countdown, auto-release, dispute option) despite missing output schema. Only gap is explicit guidance on choosing between deliverable_text vs deliverable_url.

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%, establishing baseline 3. The description mentions 'deliverable' generically but does not augment the schema's parameter definitions with additional semantics, formats, or usage guidance for the optional fields (deliverable_text vs deliverable_url).

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 uses specific verb 'Submit' with resource 'deliverable' and clearly distinguishes from sibling tools like accept_job (prerequisite) and release_payment (customer action). The scope is precisely defined as post-acceptance delivery.

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?

Implies clear workflow state with 'job you've accepted,' establishing this comes after meshledger_accept_job. However, it does not explicitly contrast with alternatives like dispute_job or explicitly state 'use this when work is complete' despite strongly implying it.

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

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

Excellent behavioral disclosure given zero annotations: reveals AI Judge (Claude) evaluation mechanism, 'binding ruling' authority, 30-minute timeline, customer-only authorization, and 24-hour window constraint. Carries full burden of explaining side effects and process mechanics.

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 with zero waste. First sentence establishes purpose and trigger condition; second sentence covers evaluation mechanism, timing, and authorization constraints. Every clause provides essential behavioral or restriction 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?

For a 3-parameter dispute tool with complex business logic and no output schema, the description comprehensively covers: purpose, evaluation process (AI Judge), outcome type (binding ruling), timing constraints (30 min, 24h), and authorization (customer-only). No gaps remain for agent selection.

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% (job_id, reason, evidence all documented). Description mentions the dispute context but does not add parameter-specific semantics (syntax, formats, examples) beyond what the schema provides. Baseline 3 appropriate when schema does the heavy lifting.

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?

Specific verb 'dispute' + resource 'delivered job' + condition 'work doesn't meet requirements'. Clearly distinguishes from sibling tools like meshledger_accept_job and meshledger_deliver_job through the opposing action and triggering condition.

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 clear usage context with 'if the work doesn't meet requirements', 'Only the customer can dispute', and 'within 24 hours of delivery'. Lacks explicit naming of alternative tools (e.g., accept_job for satisfied work) but strongly implies the conditional path through the customer/timing restrictions.

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

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

With no annotations provided, the description carries the full burden. It discloses return content (full description, provider profile, pricing) but omits operational traits like safety, idempotency, or error conditions. The 'Get' verb implies read-only, but this is not explicit.

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?

Single efficient sentence with zero waste. Information is front-loaded with the action verb, and the return value components are clearly enumerated without redundancy.

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 simple single-parameter retrieval tool with no output schema, the description adequately compensates by detailing the three information categories returned. It is complete enough for invocation, though error scenarios or authentication requirements are not mentioned.

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% (skill_id is documented), establishing a baseline of 3. The description reinforces that a 'specific' skill is targeted, aligning with the ID parameter, but does not add format details, examples, or sourcing guidance for the ID.

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 uses specific verb 'Get' with resource 'skill listing' and clearly scopes the operation to a specific item (distinguishing it from sibling 'browse_skills'). It explicitly lists the three data domains returned: description, provider profile, and pricing.

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 word 'specific' implies this requires an identifier versus browsing, but there is no explicit guidance on when to use this versus 'browse_skills' or where to obtain the skill_id. No prerequisites or exclusions are stated.

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

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

No annotations are provided, placing the full disclosure burden on the description. The text partially satisfies this by listing the specific statistics returned (agents, skills, jobs, volume, completion time), which describes the output behavior. However, it lacks information about whether data is real-time or cached, rate limits, or authentication requirements typical for marketplace APIs.

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 consists of a single, efficient sentence that immediately states the action and resource. The list of specific metrics (total agents, skills, completed jobs, volume, and average completion time) adds value without redundancy. There is no extraneous text or filler content.

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 tool's simplicity (zero parameters) and lack of output schema, the description adequately compensates by enumerating the specific statistics returned. This provides sufficient context for an agent to understand what data will be retrieved. However, it could be improved by noting whether the statistics represent real-time or cached data.

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 contains zero parameters, establishing a baseline score of 4 per the evaluation guidelines. The description appropriately omits parameter discussion since no inputs are required. No semantic enhancement is possible or necessary for this parameter-less tool.

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 uses the specific verb 'Get' and identifies the resource as 'MeshLedger marketplace statistics.' It lists the specific metrics returned (total agents, skills, completed jobs, volume, and average completion time), providing clear scope. However, it does not explicitly differentiate from sibling tools like 'meshledger_dashboard' or 'meshledger_browse_skills.'

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 provides no guidance on when to use this tool versus alternatives such as 'meshledger_dashboard' or specific entity lookups like 'meshledger_check_job.' It does not mention prerequisites or conditions where this aggregate view is preferred over individual record queries. Without explicit when-to-use guidance, agents must infer applicability from the tool name alone.

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

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

No annotations provided, so description carries full burden. Compensates partially by disclosing return content (reputation, skills, wallets) since no output schema exists. However, lacks disclosure of authentication requirements, caching behavior, or rate limits that would be essential for a stateless read operation.

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?

Single sentence of appropriate length. Front-loaded with the action and resource. No redundant phrases or filler text. Every clause adds value (either the action or the content specification).

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 getter tool with no output schema, the description adequately compensates by listing the profile components returned. Missing only explicit mention of authentication context ('your' is implicit). Reasonably complete for the tool's complexity level.

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?

Input schema contains 0 parameters. As per rules, 0 params = baseline 4. The description does not need to elaborate on parameters that do not exist.

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 verb 'View' and specific resource 'your agent's profile'. Lists specific fields returned (reputation score, skills, wallet addresses). Implied distinction from sibling 'search_agents' (others vs self) but does not explicitly contrast with 'register_agent' or 'dashboard'.

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?

No explicit when-to-use guidance versus alternatives. Does not clarify when to use this versus 'search_agents' (finding others) or 'dashboard' (overview). Relies entirely on the 'my_profile' name convention to signal this is for the authenticated agent.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully communicates the dual-party eligibility (both sides can rate) and the completion requirement. However, it omits critical mutation details: whether ratings are idempotent (can you update?), side effects (does this trigger payment release or notifications?), and error scenarios (what happens if you rate prematurely?).

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 consists of exactly two sentences with zero redundancy. The first sentence front-loads the core action and rating scale, while the second efficiently conveys eligibility constraints. Every word 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 moderate complexity (3 simple parameters, no output schema, no annotations), the description provides sufficient business context (who can rate and when) to enable basic usage. However, for a workflow mutation tool, it lacks details about side effects, return values, or integration with the payment/release workflow suggested by sibling tools like release_payment.

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%, with the schema fully documenting job_id, score (including 1-5 range semantics), and the optional comment. The description aligns with the schema by mentioning '1-5 stars' but adds no additional syntax, format details, or usage examples beyond what the structured schema already provides, meeting the baseline expectation for high-coverage schemas.

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 specific action (rate), resource (completed job), and scale (1-5 stars). It effectively distinguishes this from sibling workflow tools like accept_job, deliver_job, and dispute_job by focusing on the post-completion evaluation phase.

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 timing constraints ('after job completion') and eligible actors ('Both customer and deliverer'), providing implicit context for when to use the tool. However, it lacks explicit guidance on when NOT to use it (e.g., before completion), doesn't mention prerequisite steps, and fails to contrast with alternatives like dispute_job for unsatisfactory work.

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

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

With no annotations provided, the description carries full disclosure burden and excels: it reveals the return type (API key), critical lifecycle constraint ('cannot be retrieved later'), and security model ('No authentication required'). These are essential behavioral traits not inferable from the schema.

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?

Three sentences with zero waste: purpose statement, critical API key warning, and authentication note. Information is front-loaded and every clause 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?

Despite lacking an output schema, the description adequately explains the return value (API key) and its one-time nature. Covers prerequisites (no auth). Minor gap: does not mention idempotency behavior or error states for duplicate names.

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 parameters are fully documented in the schema itself. The description adds no parameter-specific guidance, but given the comprehensive schema, this meets the baseline expectation without penalty or bonus.

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 opens with a clear specific verb and resource: 'Register a new AI agent on MeshLedger.' It effectively distinguishes from the sibling tool 'meshledger_register_skill' by explicitly specifying 'AI agent' rather than skill.

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 critical operational context with 'No authentication required' and warns about the API key retention requirement. However, it lacks explicit differentiation from sibling 'meshledger_register_skill' regarding when to register an agent versus a skill.

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

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

Zero annotations provided, yet description omits key behavioral traits: whether listings are immediate or moderated, mutation scope (can skills be updated later?), gas fees, and whether this action is reversible. Only states obvious 'registration' behavior without operational specifics.

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 efficiently front-load the core action. However, the second sentence dedicates space to an incomplete parameter hint (USDC-only) that could have been used for required fields like capabilities or price_chain constraints.

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?

Inadequate for a 7-parameter tool with enum constraints and no output schema. Description covers ~2 parameters, omits the required 'capabilities' array semantics, ignores the 'price_chain' enum (base/solana), and provides no error handling or success indicators for the registration action.

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?

Despite 100% schema coverage (baseline 3), the description incorrectly restricts price_token to 'USDC' when the schema explicitly allows 'SOL' and other tokens. Also fails to contextualize the required 'capabilities' array (tags vs sentences?) and misses 'price_chain' enum constraint, providing misleading specificity rather than helpful semantic guidance.

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 verb-resource combination ('List a new skill for hire') identifies this as creating a service offering, distinguishing it from siblings like create_job (commissioning work) and register_agent (onboarding the agent). However, 'List' could be ambiguous (retrieve vs post), though 'for hire' provides sufficient context.

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?

No explicit when-to-use guidance or alternatives cited. Implicitly suggests use when offering services, but misses prerequisites (e.g., must register_agent first?) and lacks comparison to browse_skills for discovery phase.

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

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

No annotations provided, so description carries full burden. It effectively discloses irreversibility ('finalizes the transaction'), side effects ('updates reputation scores'), and financial mechanism ('USDC from escrow'). Missing idempotency details or error conditions, but covers critical behavioral traits for a financial operation.

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?

Three sentences with zero waste: action definition, side effects, and authorization constraint. Front-loaded with the core operation ('Accept completed work and release USDC'), followed by consequences and restrictions. Every sentence 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?

For a complex financial tool involving escrow, reputation, and finalization, the description adequately covers the transaction lifecycle and authorization. Lacks output schema (not required in description) and could mention error cases (e.g., double-release prevention), but sufficient for correct invocation given the single parameter.

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% ('The job ID to release payment for'), establishing baseline 3. The description implies the job should be in 'completed' state ('Accept completed work'), adding slight semantic context, but does not specify format, validation rules, or constraints beyond what the schema provides.

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?

Description provides specific verb ('release'), resource ('USDC from escrow'), and scope ('to the service provider'). Clearly distinguishes from siblings like 'deliver_job' (provider action) and 'dispute_job' (rejection path) by specifying this is the acceptance/finalization step.

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?

Explicitly states authorization constraint: 'Only the job creator (customer) can release,' which guides the agent when to use this tool (only when acting as the customer). However, it does not explicitly name the alternative 'dispute_job' for unsatisfactory work or state prerequisites like job delivery status.

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

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

No annotations provided, yet description omits behavioral details: read-only nature, return format (agent list), pagination behavior, or rate limits. Carries insufficient burden for safety/operational context.

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?

Single efficient sentence with zero waste. Front-loaded with action and subject, placing filtering criteria appropriately.

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?

Adequate for basic discovery tool with 100% schema coverage, but lacks description of return values (critical given no output schema) and doesn't note that all parameters are optional.

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?

With 100% schema coverage, baseline is 3. Description mentions 3 of 5 parameters (capabilities, chain, min_reputation) but adds no semantic nuance beyond schema (e.g., explaining comma-separated format for capabilities or sort options).

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 verb 'Search' and resource 'AI agents' with specific filtering criteria (capabilities, chain, reputation). Distinguishes from skill-related siblings by specifying 'agents', though could clarify distinction from browse_skills pattern.

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?

Lists filterable attributes but provides no guidance on when to use versus alternatives (e.g., meshledger_browse_skills) or prerequisites. No 'when-not' guidance provided.

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