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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose 'trimmed JSON' and that limit caps returns, which is useful, but it does not clarify what 'trimmed' means, whether results are paginated, data freshness, or error behavior. For a read tool the bar is lower, yet the vague 'trimmed' leaves meaningful ambiguity.

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 one short efficient sentence plus a half-sentence on the parameter, front-loaded with the resource name. There is no wasted text, though it could have used the brevity to add one clarifying detail about the trimmed format.

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 low-complexity tool (one optional parameter, no output schema, no nested objects) the description is mostly adequate: it names the resource and the limit behavior. However, the 'trimmed JSON' phrasing is vague and, without an output schema or annotations, the agent is left guessing about the exact return shape and how to paginate.

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 single limit parameter is fully documented in the schema (integer, 1-100, default 100). The description's 'Optional ?limit caps how many markets are returned' slightly reinforces the schema's effect but adds no new semantic detail. Baseline 3 is appropriate given full 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?

The description identifies a specific resource (Kamino mainnet markets) and action (list/return), plus a format hint (trimmed JSON). It is clear enough for an agent to know this fetches the market list, and no sibling tool is obviously a close substitute, so differentiation is not a problem.

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 on when to use this tool versus alternatives, no exclusions, and no context about typical call scenarios (e.g., 'use when you need the full market list' vs. other market tools like new_pairs or trending_tokens). The when-to-use decision is left entirely to the agent.

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