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

No annotations are provided, so the description must fully disclose behavioral traits. It does mention the need for Authorization: Bearer, which is useful, but it does not state whether the operation is read-only, what side effects (if any) occur, what the return payload looks like, or error behavior. The description is too sparse to convey the behavioral contract beyond the auth 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 extremely brief, but brevity here results in under-specification rather than conciseness. It lacks structure, no clear separation of purpose and details, and front-loads an authorization note that is more of a prerequisite than the core function. A single sentence with minimal information does not earn credit for conciseness.

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 a simple tool with two parameters and no output schema, the description should at least explain what the endpoint returns and how the parameters influence the result. It does neither. The phrase 'Bonding-curve progress' suggests a data query, but there is no indication of the response shape, units, or how ethIn affects the curve. The description is incomplete for an agent to confidently 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%, with both parameters (address and ethIn) documented directly in the schema. The description adds no additional parameter context, but the baseline for high schema coverage is 3. The description does not clarify how ethIn affects the curve or what the response might be, but the schema already covers the format and purpose of each 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?

The description 'Bonding-curve progress' is a noun phrase with no verb; it does not clearly state the action performed (e.g., retrieve, fetch, or compute). It gives a domain hint but not a precise operation, and it does not distinguish itself from sibling tools like get_token or get_agent. The resource and the meaning of 'progress' remain ambiguous.

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?

There is no guidance on when to use this tool versus alternatives. The description only notes an authorization requirement, which is a prerequisite, not a usage condition. No context is given about scenarios, exclusions, or related tools that might be more appropriate.

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