Tracea

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

With no annotations, the description carries the full burden and does well: it discloses that the tool is a dry-run (no execution), performs on-chain checks, and returns an explicit structure { allowed, reason }. It also details what conditions are checked, which goes beyond a basic read-only hint.

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 a single, well-structured sentence that front-loads the most important information (dry-run before execution) and then packs in the checks and return format. Every clause adds value with no redundancy or filler.

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 3 fully documented parameters and no output schema, the description provides the return value shape and explains the criteria, which covers the essential context. It could further elaborate on what the 'reason' might contain, but the tool's simplicity and the clear return type make this adequate.

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 the baseline is 3. The description adds minimal extra meaning beyond the schema: it clarifies agent_address as the smart account address and explains that destination approval depends on a whitelist, but these are already partially implied by the parameter descriptions. No significant enhancement.

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 purpose: a dry-run check for payment allowance. It uses a specific verb ('Dry-run') and identifies the resource (payment) and the specific checks performed (permission, cap, whitelist). It also distinguishes itself from sibling tools like payment_status or payment_required by explicitly framing it as a pre-execution check.

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 clear usage timing ('BEFORE executing it'), implying when to use the tool. It does not mention alternatives by name, but the context of checking before execution gives sufficient guidance for an agent selecting this tool from a payment-related sibling set.

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, so the description carries the full burden. It specifies a read operation and the returned fields, but does not mention revert behavior for invalid IDs or other edge cases. The word 'Read' implies non-mutating, but no explicit safety guarantee is given.

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 two concise sentences, immediately identifying the operation and outputs. No redundancy or filler; well-structured and front-loaded.

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 read tool, the description covers what it does and what it returns. It does not address edge cases like non-existent IDs, but the essential information for selection and invocation is present. Given the lack of output schema, listing the return fields provides sufficient context.

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 already documents the single parameter with 100% coverage ('Numeric action ID'). The description adds only the phrase 'by its numeric ID,' which does not provide additional semantics beyond the schema. 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 reads a single logged agent action from the Tracea ActionLog contract using a numeric ID. The verb 'Read' and the scope 'single' effectively distinguish it from sibling tools like get_agent_actions.

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 phrase 'single... by its numeric ID' implies this is the tool to use when a specific action ID is known, contrasting with list-style siblings. However, it does not explicitly name alternatives or state when not to use 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?

No annotations are provided, so the description must fully disclose behavior. It only states the purpose and implies a read operation through 'List', but doesn't explicitly confirm read-only safety, pagination, ordering, or other behavioral traits. This is a significant gap for a tool with no annotation support.

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 a single, front-loaded sentence with no filler. It earns its place by immediately announcing the action ('List') and the resource, making it efficient and easy to parse.

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 one-parameter tool with no output schema or annotations, the description provides enough to understand what is returned (a list of action IDs) and what input is needed. It lacks caveats like pagination, but for the tool's simplicity, it is adequately complete.

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 schema covers 100% of parameter semantics with a clear description ('Ethereum address of the agent'). The tool description merely restates 'a given agent', adding no new meaning beyond the schema. 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 uses a specific verb 'List' and clearly specifies the resource: 'on-chain action IDs logged for a given agent'. It distinguishes from siblings like get_action (singular action) and log_action (write operation) by focusing on listing all action IDs for an agent.

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 states the context of use ('for a given agent') and the tool's function, making it clear when to choose this tool. However, it doesn't explicitly mention alternatives or exclusions, which would push it to a 5.

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, so the description carries the full burden. It adds value by specifying 'raw' and listing return fields, but does not explicitly confirm read-only behavior or describe error handling. The verb 'get' weakly implies safety, but this is not disclosed.

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 a single sentence, front-loaded with the action and resource, and uses only necessary words. It is elegant and concise.

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 one-parameter read tool, the description adequately conveys the purpose and return contents. However, it omits handling of missing agents and does not differentiate from sibling tools, leaving some context gaps.

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 schema already provides a description for agent_address ('Ethereum address of the agent'), covering 100% of parameters. The tool description adds no additional meaning beyond what the schema already states, so the baseline of 3 applies.

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 (get) and the resource (raw Tracea registry record), and enumerates specific fields (owner, permission scope, financial cap, active status, timestamps). This distinguishes it from sibling tools that operate on actions, revocations, or verification.

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?

Usage context is implied by the focus on raw registry data, but there is no explicit guidance on when to use this tool over verify_agent or is_agent_revoked. No alternative tools are mentioned, so the agent must infer boundaries.

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 takes full responsibility for behavioral disclosure. It explicitly warns that the private key is returned only once and advises secure storage, which is critical. It also notes the activation code is one-time, adding essential transparency about 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?

The description is two sentences, front-loading the purpose and following with a critical security warning. Every word contributes essential information; there is no redundancy or filler.

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 and output schema, the description adequately covers the tool's purpose, the specific data returned, and the crucial one-time behavior. It could mention error conditions or prerequisites, but for a sensitive credential retrieval tool, this is a sufficiently complete description.

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 already has 100% coverage with descriptions for both parameters. The description adds context that the activation code comes from the owner and emphasizes the one-time nature, but provides no further syntax or format details. This is marginal added value beyond the schema, so the baseline of 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: retrieving the agent's full Tracea identity, listing specific components (apiKey, private key, smart account address). The verb 'Get' plus the detailed resource makes it distinct from sibling tools like get_agent_info, which likely returns public info rather than sensitive credentials.

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 clear context: use when you need the full identity and possess the owner's one-time activation code. It does not explicitly name alternative tools or state when not to use, but the sensitive nature and activation requirement make the usage context well understood.

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?

There are no annotations, so the description carries the full burden. The phrase 'List all' implies a read-only, non-destructive operation, but it does not disclose return format, pagination, error handling, or behavior for invalid addresses. The core behavior is clear, but additional context is missing.

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 a single, direct sentence with no redundancy. Every word contributes meaning: 'List all agent addresses registered on Tracea by a given owner address.' It is efficiently structured and front-loaded.

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?

This is a simple one-parameter list tool with no output schema and no annotations. The description adequately states what it returns (agent addresses) and the input condition (owner). It could further clarify whether the list includes all statuses (e.g., revoked agents) or the return shape, but overall it is sufficiently complete for a basic lookup.

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 provides a full description for the only parameter 'owner_address' (Ethereum address of the owner), giving 100% schema coverage. The description's phrase 'by a given owner address' adds no new semantics beyond the schema. Baseline 3 applies because schema coverage is high.

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 states 'List all agent addresses registered on Tracea by a given owner address,' which clearly identifies the action (list), the resource (agent addresses), and the scoping condition (owner address). This distinguishes it from sibling tools like get_agent_info or get_agent_actions, which target different resources or scopes.

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 when to use the tool (when needing agent addresses for a specific owner) but does not explicitly state alternatives, exclusions, or prerequisites. Sibling tools are available but not referenced. This is adequate but not explicit.

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 explains the semantic meaning of the returned list (empty vs. non-empty) and frames the tool as an 'anti-injection guardrail,' which is useful context. However, it does not mention potential errors (e.g., invalid agent address) or authorize requirements, which would enhance transparency.

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 exceptionally concise: two sentences that immediately convey the tool's purpose and the key behavioral nuance. It avoids redundancy, front-loads the main verb and resource, and every sentence 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 simple read tool with one parameter and no output schema, the description is largely complete. It explains what is returned (a list of addresses) and the meaning of empty vs. non-empty lists, which is critical for correct usage. It does not describe the exact return type (e.g., array of strings) but that is strongly implied by the term 'list.'

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 already provides 100% coverage with a single parameter 'agent_address' described as 'Ethereum address of the agent.' The description does not add any additional meaning beyond the schema, such as formatting examples or constraints, so a baseline score of 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 purpose: 'Get the list of owner-approved payment destination addresses for an agent.' The phrase 'anti-injection guardrail' adds specific context that distinguishes it from sibling tools like check_payment_allowed, making the resource and its intent unambiguous.

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 clear usage context by explaining the guardrail behavior: 'Non-empty list = the agent's smart account can ONLY pay these addresses. Empty = all allowed.' This helps the agent understand when this tool is relevant (e.g., before initiating a payment), though it does not explicitly compare against sibling tools or state exclusions.

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 for behavioral disclosure. It states the output content ('registration file' including KYA block) and implies a read operation via 'Fetch', but does not mention potential errors (e.g., agent not registered), return format, or prerequisites beyond the implicit registration requirement.

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 a single front-loaded sentence that uses concise, specific language without waste. Every phrase earns its place, efficiently conveying the tool's purpose and key detail about the registration file.

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 tool is simple (one param, no output schema), and the description adequately states what it returns, but it lacks details about output format, error conditions, or whether the address must be currently registered. For a minimal tool it is sufficient, yet some edge behavior is left unspecified.

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 schema covers the parameter with a basic description ('Ethereum address of the agent'), and the tool description adds meaningful context by specifying that the agent must be 'Tracea-registered'. This goes beyond the schema's generic address description, clarifying the expected input domain.

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 a specific verb ('Fetch'), identifies a clear resource ('ERC-8004 compatible registration file'), and adds a distinguishing detail ('including the KYA legal principal block'). This clearly distinguishes it from sibling tools like get_agent_info or get_agent_actions.

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 usage context by specifying 'for a Tracea-registered agent' and mentioning the KYA block, but it does not explicitly state when to use this tool over siblings or mention exclusions. There is no alternative tool named, so guidance is only implied.

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, so the description carries the full burden, and it does substantial work: it discloses what the returned card contains and that the response includes a ready-to-share link plus machine-readable JSON endpoints. It omits auth/permission requirements and failure behavior, so it is strong but not exhaustive.

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, front-loaded with the primary purpose and return value. Dense with useful detail and little waste, though the middle sentence is a long clause chain that could be tightened.

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?

With no output schema, the description compensates by describing the return payload (shareable link plus JSON endpoints) and the card's contents. No annotations exist to cover safety behavior, but for a read-style getter with fully documented params, the remaining gaps are minor.

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% and both optional params carry enum descriptions, so the schema already documents lang and niveau. The only added meaning is clarifying that 'standard' is the publicly exposed disclosure level; the rest restates the schema, matching the baseline of 3.

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 and resource: 'Get the public URL of an agent's Tracea KYA verification card,' and it enumerates what the card presents (mandant entity, permission scope, financial cap, proof hash). The purpose is unambiguous, but it never names or contrasts with near-siblings like verify_agent or get_agent_info.

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?

Gives a clear intended use — 'Use it to hand a verifier a link' — which tells the agent the context in which this is the right tool. It offers no exclusions or alternatives (e.g. when to prefer verify_agent instead), so it stops short of full routing 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 are provided, so the description carries the full burden. The verb 'Check' strongly implies a read-only operation, and the mention of revocation types adds useful context. However, it does not disclose behavior such as return format, error conditions, or whether the tool interacts with external systems beyond what's implied.

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 a single, well-structured sentence with no wasted words. It front-loads the action verb and immediately states the tool's purpose, making it highly concise.

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 one-parameter read-only tool without an output schema, the description is adequately complete. It explains the core purpose and types of revocation. It could explicitly state that it returns a boolean (true/false), but the name and verb 'Check' already imply this, so the gap is minor.

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% for the single parameter, so baseline is 3. The description does not add any additional meaning about the agent_address parameter beyond what the schema already provides ('Ethereum address of the agent').

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 a specific verb ('Check') and resource ('agent's mandate has been revoked on Tracea'), clearly distinguishing this from sibling tools like get_agent_info by focusing on revocation status. It also adds nuance with 'immediate, scheduled or partial revocation', making the purpose unambiguous.

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 clearly indicates the tool checks whether a mandate is revoked, which gives context for use. However, it does not explicitly state when not to use it or compare it to siblings like get_agent_info, so it lacks explicit exclusions or alternative 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?

The description discloses several behavioral traits: the record is immutable and court-ready, the tool requires a specific env var (TRACEA_API_KEY), and the action is signed by the wallet. These go beyond the raw purpose and inform the agent of security and permanence implications.

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 two sentences long, front-loads the action with 'Log', and includes essential contextual details (immutability, API key, signing) without any fluff. 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?

While the description covers key aspects, it omits the return value (e.g., transaction ID) and potential side effects like gas costs or failure modes. With no output schema and no annotations, the agent has no information about what to expect after invocation, leaving a notable gap.

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 already describes all three parameters with 100% coverage. The description does not add additional parameter-specific details nor clarify relationships between parameters, so it does not exceed the baseline established by 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?

The description uses the specific verb 'Log' with the resource 'agent action on-chain via Tracea', clearly stating the tool's purpose. It distinguishes itself from all sibling tools, which are read/verify operations. This is a precise and unambiguous definition.

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 usage context by being the only write/log tool among readonly siblings, making it obvious when to use it. However, it does not explicitly state when not to use it or mention alternative tools, though the sibling names themselves clarify this.

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, so the description discloses the key side effect ('mark the session fulfilled') and the return behavior. Yet it omits prerequisites (e.g., prior payment_required call), idempotency, or reversibility, leaving gaps for an agent.

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, each earn its place: action, trust principle, and return/error behavior. No wasted words; front-loaded with the core purpose.

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?

Without an output schema, the description specifies return shape ({ status: 'fulfilled', resource }) and error cases (not yet paid/expired). It covers the essential behavior but lacks guidance on when to use this vs. payment_status, leaving slight ambiguity.

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 clear descriptions for both parameters (payment_id, tx_hash). The tool description does not add extra semantics beyond what the schema already conveys, so a baseline of 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 verifies a x402 payment on-chain (USDC transfer to your address, exact amount) and marks the session fulfilled. It distinguishes from sibling payment tools by emphasizing on-chain verification as the sole source of truth.

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?

It provides context that the blockchain is the only trusted source and the payment_sessions table is never trusted alone, implying this tool is for authoritative on-chain verification. However, it does not explicitly contrast with payment_status or payment_required.

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, the description carries the full burden. It transparently explains the on-chain enforcement, the required follow-up call, and the need to wait for payment_incoming. But it does not mention permissions, side effects, or what happens if the payment session expires. This is a meaningful gap for a tool that creates a financial request.

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 three sentences, front-loaded with the core purpose, then return values, then the required workflow. Every sentence adds essential information and there is no filler or 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 tool with no output schema and no annotations, the description covers the key elements: what it creates, what it returns, the on-chain call the payer must make, and when to deliver the resource. It could mention expiry or failure modes, but the existing content is sufficient for an agent to invoke the tool correctly.

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 baseline is 3. The description adds no extra detail about the parameters themselves; it only reuses destination and amount in the context of return values. The schema already explains all parameters, so the description provides marginal benefit here.

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 states the exact purpose: 'Create a x402 payment request (HTTP 402) for a resource you sell to another agent.' It uses a specific verb and resource, and the mention of returning payment details and the follow-up contract call clearly distinguishes it from sibling tools like payment_incoming and payment_status.

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 clear context: use it when selling a resource to another agent. It also provides a workflow instruction ('Deliver the resource only after payment_incoming confirms fulfilment') that implies when to wait for payment. However, it does not explicitly name alternatives or state when not to use this tool, so it lacks explicit exclusions.

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, so the description carries the burden. It discloses the returned status values and fields, and the 'Get' and 'poll' wording implies a non-mutating read operation. It does not detail permissions or side effects, but for a status getter this is sufficient.

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 two sentences, front-loaded with the action and then return details and usage. Every clause contributes meaning; no redundancy or filler.

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?

With no output schema, the description adequately explains return contents (status, destination, amount, tx hash), the source of the input parameter, and a typical usage scenario. For a simple one-parameter getter, this is complete.

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%: payment_id is described as 'The paymentId returned by payment_required (pay_...)'. The tool description adds no further parameter details, so it merely meets the baseline without adding extra meaning.

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 ('Get the status of a x402 payment session') and specifies the resource and return fields (statuses, destination, amount, tx hash). This distinguishes it from sibling tools like payment_required or payment_incoming, which handle payment creation/receipt.

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 explicit usage context: 'Useful to poll while waiting for the paying agent's on-chain transaction.' It does not name alternative tools or exclusions, but the polling use case is clear enough to guide selection.

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 that it is off-chain, free, and instant, and explains the auth mechanism (via MCP URL key or self-activation with a one-time code). However, it does not describe what happens after reporting (e.g., response format, side effects) or any rate limits, which are relevant for an action-reporting 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?

The description is concise (three sentences) and front-loaded with the core purpose, then usage, then auth details. Every sentence adds value; there is no redundant 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?

The description covers the tool's purpose, usage timing, and auth requirements, which is substantial for a tool with no output schema and no annotations. However, it does not explicitly explain return values, differentiation from sibling tools like log_action, or the significance of optional fields like in_permission and permission_label, though those are in the schema. Overall, it is quite complete for its complexity.

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 all six parameters have descriptions in the schema itself. The tool description adds minimal parameter-specific information beyond that, focusing mainly on when to call and auth. It does not elaborate on parameter semantics, so the baseline of 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 purpose: 'Report an action the agent just performed to its owner's Tracea activity feed.' It specifies the resource (activity feed) and the verb (report), and distinguishes it from siblings by noting it is off-chain, free, and instant. The scope ('AFTER every significant action') is explicit.

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 clear when-to-use guidance: 'Call this AFTER every significant action' with concrete examples like email sent, message posted, file modified, payment, purchase, and booking. It does not explicitly mention when not to use it or contrast with sibling tools like log_action, but the context is strong.

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, the description carries the full burden and does well: it discloses immutability ('seal ... immutable on-chain proof'), re-validation before anchoring ('re-checks everything'), an authorization requirement, and the returned artifacts. It stops short of stating cost/gas implications or what happens on a repeat call against the same id, which are the remaining behavioral gaps for an irreversible on-chain write.

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 tight sentences, front-loaded with what the tool does, then the precondition, then the auth requirement and return values. Every sentence carries information the agent needs; nothing is restated from the schema or name.

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 mutation tool with no annotations and no output schema, the description covers purpose, precondition, authorization and return artifacts, which is enough to call it correctly. The nested 'donnees' object's shape and any failure/idempotency behavior remain unspecified, keeping it just short of fully complete.

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 schema already documents id, donnees and agent (including the crucial 'Same data object that passed tracea_check_demarche' note). The description adds no parameter-level detail such as format or coupling of 'donnees' to the previous check, so it sits at the baseline.

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?

States a specific verb and resource ('Seal a validated file as an immutable on-chain proof') with the chain context (Tracea Online, Base). It also names the sibling it depends on (tracea_check_demarche) and the artifact it returns, so an agent can distinguish it from tracea_signature or tracea_demarche_preuve immediately.

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?

Explicit precondition: 'Call this ONLY after tracea_check_demarche returned ok:true', which is both a when-to-use rule and an exclusion. It adds a second gating condition — 'Requires the caller to be an authorized harness' — so the agent knows whether it is even eligible to invoke this tool.

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, the description carries the full burden and handles it well: it discloses the external-registry cross-check behavior (network/validation dependency beyond local schema checks) and the exact return contract ({ ok: true, recordHash } vs { ok: false, errors }). It stops short of stating idempotency, rate limits, or whether any state is persisted.

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?

Front-loaded with the core purpose, then return shape, then the imperative sequencing rule – each sentence earns its place. The bolded caps ('THE', 'ALWAYS') are emphatic but not wasteful, though they push slightly toward verbosity.

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 having no output schema, the description inlines both success and failure response shapes, names the external validation dependency, and states the required call ordering. Nothing essential for invoking the tool correctly is missing.

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% and both parameters (id, donnees) are documented in the schema, so the baseline is 3. The description only reinforces that donnees fields must match tracea_demarche_schema, adding no format or constraint detail beyond the structured field docs.

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?

States a specific verb+resource ('check' / validate submitted démarche data) and adds the distinguishing mechanism: validation against the official procedure schema plus cross-checking critical values against French registries (SIRET/INSEE Sirene). This clearly separates it from siblings like tracea_anchor_demarche and tracea_demarche_preuve.

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?

Explicit sequencing guidance: 'ALWAYS call this BEFORE telling the user the file is ready' and 'fix the exact fields reported' tells the agent exactly when to invoke it and what to do after. It also points to tracea_demarche_schema as the source of field names, but does not state explicit exclusions or when NOT to call 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?

With no annotations, the description carries the full burden and does well: it discloses the backend generator call, that the dossier is persisted for the visitor's agent, the return payload, and the failure mode (ok:false + champsManquants) with an explicit rule against fabricating partial documents. It does not mention auth/permission requirements, which is the only notable gap.

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 tight sentences: capability first, then ordering constraints, then failure behavior. Every sentence earns its place with no filler.

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 mutation tool with a nested object payload and no output schema, the description covers the side effects, sequencing, and return shape adequately. It could say more about prerequisites (e.g. required identity/auth) or what happens when the document is regenerated.

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 schema already documents id, agent and donnees with their formats and warnings. The description adds only the 'same fields as tracea_demarche_schema' cross-reference, so the 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?

States a specific verb and resource ('Prepare le document officiel d'une demarche (CERFA ou demarche libre) et le rend signable'), and names the downstream artifacts (reference + PDF path). It is clearly distinguishable from sibling tools like tracea_signature and tracea_check_demarche.

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 ordering relative to siblings: 'A appeler APRES tracea_check_demarche (ok:true) et AVANT tracea_signature'. The precondition and alternative flow are spelled out, leaving nothing to inference.

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, the description carries the full burden and does state the two properties an agent most needs: 'Read-only and free', which covers both the readOnly safety profile and cost. It further implies the returned facts (anchored?, when, operator, rule version), partially covering output despite no output schema. It stops short of describing failure behavior for an unknown hash.

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, front-loaded with the purpose and followed by the input provenance; every clause carries information and none is filler.

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 single-param read-only verification tool with no output schema, the description supplies purpose, input provenance, key return facts, and safety/cost profile. The only omission is behavior on an unknown or malformed hash, which is minor for this tool class.

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% and the schema already documents the hash as a 0x... 32-byte value, so the baseline is 3. The description adds genuine meaning beyond the schema by tying the parameter to its producing tools, telling the agent where the value must come from rather than just its format.

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 (verify) plus resource (an existing anchoring proof), and it names exactly the questions answered: whether the file was anchored, when, by whom, and under which rule version. It is cleanly distinguishable from the sibling tracea_anchor_demarche, which creates rather than verifies.

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?

It tells the agent the precondition for calling it: 'Use the recordHash returned by tracea_check_demarche / tracea_anchor_demarche', which is effectively a routing rule to the sibling tools that produce the input. No explicit when-not-to-use case, but the usage context is unambiguous.

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, so the description must carry the behavioral load, and it does the most important part: it specifies the exact return payload (name, type, required, format/pattern, bounds, example), which is critical because there is no output schema. Remaining gaps are error behavior for an unknown id and any permission requirement, and read-only status is only implied by 'Return'.

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 tight sentences, front-loaded with the return contract, then sequencing, then the payoff. Nothing is padded, though the closing 'Prevents hallucinated fields' is value framing rather than new 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?

With no output schema, the description compensates by enumerating the returned fields, and the required id plus its originating tool are both documented. Only failure/permission behavior for an invalid procedure id is left unaddressed.

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% and the single 'id' parameter is documented with an example value, so the schema already does the parameter work. The description only says 'a given administrative procedure' without adding format guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Return exactly which fields a given administrative procedure requires') and enumerates the returned field attributes, so it is clearly distinguishable from sibling tracea_list_demarches. An agent knows precisely what this tool produces without opening a schema.

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 prescribes the sequencing: 'Call this after tracea_list_demarches', and gives the downstream reason (ask the user ONLY for the real fields). It does not name a case where this tool should be skipped, but the ordering constraint against the sibling is clear and actionable.

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, the description carries the full burden and does useful work: it discloses the return content (exact procedure IDs) and explains a returned field semantic, `schemaPret: true` meaning guided/anti-rejection mode is available. It stops short of stating auth needs, rate limits, or the full response shape.

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 short sentences, zero filler, and the highest-value instruction ('ALWAYS call this first') is front-loaded immediately after the purpose statement.

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-param, no-annotation, no-output-schema tool, the description covers purpose, call ordering, and one key return field. It does not enumerate the other fields the list returns, so an agent knows the shape only partially.

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 takes zero parameters, so the schema has nothing to document and there are no argument semantics to clarify. Baseline of 4 applies for a no-parameter 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?

States a specific verb (List) and resource (administrative procedures Tracea supports), and makes its output concrete: procedure IDs and the CERFA form mapping. This clearly separates it from siblings like tracea_check_demarche or tracea_demarche_schema, which operate on a single procedure.

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?

'ALWAYS call this first' gives an explicit sequencing directive with a rationale (so the AI never has to guess which form applies). It is strong on when-to-use, but names no alternative or exclusion condition for cases where listing is not needed.

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 the description carries the full burden, and it does disclose meaningful side effects: it sends invitations and generates per-signatory links, and it documents the failure mode when pdfPath/signataires are absent. It omits permissions, idempotency, and the demo/prod environment behavior, so it is strong but not exhaustive.

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, front-loaded with the action verb and its consequences, followed by the hard requirement. No filler; every clause adds information about behavior or preconditions.

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 7-parameter mutation tool with no output schema and full schema coverage, the description supplies what the structured fields cannot: the real-world side effects and the mandatory inputs. Return values need not be explained (no output schema), and the 'no link returned' note covers the key outcome, though environment/auth context is absent.

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 schema already documents each parameter; baseline is 3. The description usefully reinforces that pdfPath and signataires are truly required (the schema lists 0 required) and ties the signature zone to the box concept, but adds no syntax or format detail 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?

The description gives a specific verb and resource ('DEPOSE REELLEMENT le document prepare dans Tracea Sign') and enumerates the concrete actions performed (creates signatories, places the signature zone, produces a per-person link, sends invitations). It implies contrast with a mere check via the capitalized 'REELLEMENT', but never names a sibling tool such as tracea_check_demarche, so differentiation is left implicit.

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?

It states the operating condition that pdfPath and signataires are mandatory and that without them no link is returned, which effectively tells the agent when the call can succeed. However it offers no explicit when-to-use/when-not guidance relative to the other tracea_* tools or prerequisites like prior preparation.

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, so the description carries the full burden. It adds value by disclosing the return fields (registration status, financial cap, etc.) and the 'when available' qualifier for the mandant, but it does not disclose potential errors, network dependencies, or side effects (though read-only is implied).

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 well-structured sentences. The first states purpose and output; the second provides usage guidance. No waste, fully front-loaded with the core purpose.

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 one-parameter tool with no output schema and no annotations, the description covers purpose, return values, and usage context sufficiently. It is complete for an agent to select and invoke appropriately.

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 schema fully describes the single parameter 'agent_address' with its format, achieving 100% coverage. The description does not add additional parameter semantics, so the baseline of 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 uses a specific verb 'Verify' with a clear resource ('AI agent's on-chain legal identity on Tracea (Base Sepolia)') and enumerates the specific verification attributes returned. This distinguishes it from sibling tools like 'get_agent_info' by emphasizing the legal identity verification purpose and the 'BEFORE trusting' use case.

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 when to use: 'Use this BEFORE trusting or delegating work to an agent.' This provides clear context for adoption. However, it does not mention alternatives or when not to use, so it falls short of the full 5 criteria.

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