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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered externally. The description adds the '(free)' billing signal, which is genuinely useful context not present in annotations, but says nothing about pagination, ordering, or shape of the returned counts. With annotations carrying the safety profile, a 3 is appropriate.

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?

Four words with zero padding, and the resource is front-loaded ahead of the '(free)' qualifier. It is efficient, though so terse that it borders on under-specification rather than ideal concision.

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 no-argument, read-only listing tool with no output schema, the agent mainly needs to know what comes back; 'body systems with peptide counts' covers that at a minimal level. It leaves open the return shape (list of names plus integer counts) and ordering, which is the only real 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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and fully described, leaving no gap the description needs to fill.

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 fragment 'Body systems with peptide counts' identifies the resource and what accompanies each entry, so an agent can guess it enumerates body-system categories. But it is a noun phrase with no verb and no differentiation from the sibling list_peptides, so the agent must infer that this is the taxonomy-level listing rather than a peptide listing.

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?

'(free)' hints that this call has no cost/credit implication, but there is no statement of when to choose this over list_peptides or search, no prerequisite, and no exclusion. Usage must be inferred entirely from the name.

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