EuroRWA Analyst

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context about the alert categories and includes severity, but it does not explicitly state whether the operation is read-only, whether there are any side effects, or how the output is structured.

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, dense sentence that efficiently conveys the tool's purpose and key output characteristics without unnecessary 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?

While the description covers the source and categories of alerts, it lacks an explicit description of the return format or fields. Since there is no output schema, this omission creates some uncertainty for an agent about the exact structure of the response.

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, so there is nothing for the description to explain. The baseline for no-parameter tools is 4, and the description appropriately avoids redundant parameter details.

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 identifies the tool as a provider of operational alerts from EuroRWA, enumerating specific alert types like yield breakouts, TVL spikes, and severity. It distinguishes itself from siblings (analytics, funds, overview) by focusing on alerts, though it lacks an explicit verb such as 'get' or 'list'.

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 that this tool should be used when an agent needs the latest monitor alerts, but it provides no explicit guidance on when to choose it over sibling tools like analytics or overview. No alternatives or exclusion criteria are mentioned.

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 of behavioral disclosure. It only enumerates data content and does not mention whether the tool is read-only, requires authentication, or has any rate limits or data freshness constraints. For a zero-parameter analytics tool, this is a 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?

The description is a single, front-loaded sentence that lists all relevant metrics without any fluff. It is dense but well-organized 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?

With no output schema, the description effectively lists the return content (TVL, concentration splits, yield metrics, holders, flows). It could additionally specify data timeframe or source, but for a no-parameter tool it is sufficiently 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 tool has no parameters, so the baseline is 4. The description adds no parameter-specific details, but none are needed given the empty 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 clearly states that the tool provides institutional analytics for the tokenized money-market sector and lists specific metrics (TVL, concentration, yields, splits, holders, flows). This distinguishes it from a generic 'overview' but does not explicitly contrast with sibling tools.

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 no guidance on when to use this tool versus alternatives like 'alerts', 'funds', or 'overview'. There are no explicit exclusions or context indicating when analytics is preferred.

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 burden. It states the data is a 'Latest snapshot' and includes 'integrity checks', implying some validation, but it does not specify whether the tool is read-only, data freshness, or any limitations. There is no explicit statement about side effects or permissions, though it is implicitly read-only.

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, well-structured with a colon separating the main idea from the list of fields. It is brief and free of redundant wording, though it could benefit from an explicit verb for clarity.

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 absence of annotations, output schema, and parameters, the description provides a reasonable overview but leaves ambiguities: the meaning of 'integrity checks' is unclear, and there is no statement about data coverage or refresh cadence. The tool is simple, but for a complete picture, more behavioral context would be helpful.

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 has zero parameters, making schema coverage trivially 100%. The description adds meaningful context about the returned snapshot contents, such as specific metrics and sort order, which compensates for the lack of parameters. Baseline 4 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 identifies the tool's function as providing a snapshot of tokenized money-market funds, listing specific data fields (TVL, 7d change, yield, holders, integrity checks) and sorting by TVL. While lacking an explicit verb like 'get', the phrase 'Latest snapshot' conveys a retrieval/read action. It distinguishes from siblings like alerts and overview by focusing on fund-specific metrics.

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 guidance is given on when to use this tool versus alternatives. The description does not mention whether this is the go-to source for fund data, nor does it exclude other tools for different use cases. Sibling tools like analytics and overview are not referenced, leaving the agent to infer 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, the description carries the full burden and does well by disclosing that the report is hashed, signed, and attested on-chain (Sepolia) for independent verification. This adds meaningful behavioral context beyond simple retrieval, though it omits potential error cases or data freshness caveats.

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: two sentences that efficiently pack the report contents and the on-chain verification mechanism. Every sentence earns its place, with no fluff 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?

Despite having no output schema and no annotations, the description fully explains what the tool returns and its verification property. It is complete for an overview tool with zero parameters, covering both the content and a distinctive behavioral trait.

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 has zero parameters, so the baseline is 4. The description does not need to add parameter details and correctly avoids inventing any, making invocation straightforward.

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 identifies the tool as an 'EuroRWA analyst overview' that provides a detailed report with BUY/HOLD/SELL signals, reasons, market view, crypto brief, and on-chain brief. This specific verb+resource combination distinguishes it from sibling tools like alerts, analytics, and funds.

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 for obtaining the latest tokenized money-market fund report, but it does not explicitly state when to use this tool versus alternatives. No comparative guidance is given, leaving the agent to infer based on the content described.

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