Lends Get Protocol State

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

The annotations already cover the safety profile with readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value beyond those annotations by promising a block-consistent snapshot and noting the state is public, which clarifies consistency behavior and access expectations. No contradiction with annotations.

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, tightly written sentence with no filler. The read verb is front-loaded, and each qualifier ('block-consistent', 'public', 'protocol and PSM state') contributes meaningful 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 zero-parameter, read-only tool with rich annotations covering safety and external-world behavior, the description is complete enough to invoke correctly. The absence of an output schema is not a significant gap because the description and title sufficiently indicate what is being read.

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 the description carries no parameter-documentation burden. The baseline of 4 applies, and the description's mention of 'block-consistent snapshot' also clarifies the nature of the result the agent should expect from a no-argument call.

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 ('Read') plus a clear resource ('public LENDS protocol and PSM state') and a distinctive qualifier ('block-consistent snapshot'). This clearly distinguishes it from narrower sibling getters such as lends_get_markets, lends_get_position, and lends_get_staking_state.

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 aggregate state getter versus the many specific getters in the sibling list. There are no explicit use-case conditions, exclusions, or alternatives mentioned, so an agent must infer the intended context from the tool name and sibling names.

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