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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond annotations: the data source is the SEC weekly return, and each record carries returns, manager, and page — useful for an agent with no output schema.

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?

Dense and front-loaded: the source and result shape come first, then the filter/sort dimensions, then the returned fields. No filler, though the final fragment listing returns is slightly list-like.

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?

With no output schema, the description usefully names what each fund returns, and covers all filter/sort dimensions of a 6-param tool. It is nearly complete; only pagination/limit behavior and the exact default sort mechanics are left implicit.

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 67% and the description expands the opaque sort_by enums (r1m, ytd, r2025, r1y, r3y) into human terms (last month, year to date, 2025, one year, three years) and confirms query/manager/category/currency filters. Only 'limit' is left solely to the schema.

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: it retrieves Nigerian mutual funds from the SEC weekly return with filtering and sorting. The scope (filtered/sorted list of funds) is clearly distinct from the singular get_mutual_fund, league table, and market summary siblings, though no sibling is named explicitly.

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?

Implicit usage is clear (search/filter funds by name, category, manager, currency and rank by return), and the sort options hint at typical use. No explicit when-to-use versus alternatives (e.g. compare_pension_vs_mutual_funds or get_mutual_fund_league_table) or exclusions are given.

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