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

With readOnlyHint=true and openWorldHint=false already declared, the safety profile is covered, and the description adds real behavioral context: results are paginated and next_offset must be passed back as offset. The dependency on get_esg_metadata for valid enum-like values is also disclosed, though error/empty-result behavior is not.

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?

Three tight sentences, front-loaded with the purpose, then usage, then the pagination mechanic and prerequisite. Every sentence carries distinct information with no repetition of the schema.

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 read-only, zero-required-parameter listing tool with a full schema and an output schema, the description covers purpose, usage, pagination, and the prerequisite lookup. Return-value shape is delegated appropriately to the output schema, leaving little missing.

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% and every parameter (limit, query, offset, pillar, section) is already documented in the schema, including the next_offset convention for offset. The description restates the filter dimensions in prose without adding syntax or format detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('List and filter ESG Hub articles') plus the three filter axes (section, pillar, title substring), so the agent knows exactly what the tool returns. It does not differentiate itself from the similar-sounding siblings search_esg or list_esg_resources, which is why it falls short of a 5.

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?

Gives clear positive usage ('browse the knowledge base or enumerate a domain') and an explicit prerequisite ('Call get_esg_metadata first to discover valid section/pillar values'), which is genuinely actionable guidance. It stops short of naming when to prefer search_esg over this listing tool, so no explicit exclusion is stated.

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