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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: deterministic alphabetical ordering, no relevance ranking, no query surface, and an output-fidelity instruction ('Preserve returned URLs exactly'). It stops short of describing pagination behavior, which the schema handles.

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 sentences, each doing distinct work: what it returns, how it differs from search, and how to invoke it. The scoping claim is front-loaded and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return-value documentation is not required, and the annotations carry the safety profile. The description still supplies the ordering guarantee and the URL-preservation caveat an agent needs, leaving nothing material missing for a two-optional-parameter list tool.

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%, so both limit and offset are already documented with bounds and defaults. The description's 'Call it with no arguments to list everything' corroborates the optional-paging design but adds no syntax or semantics beyond the schema. Baseline 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 every TAAFT feature') and enumerates the returned fields (id, name, slug, TAAFT URL, tool count, model count). The framing as a 'complete alphabetical listing, not a search' cleanly separates it from the many search_* siblings and from list_feature_models/list_feature_tools.

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?

Explicitly states when to use it ('Call it with no arguments to list everything') and when not to ('there is no query and no relevance ranking'), which routes the agent away from the search_* family. Both the usage condition and the exclusion are stated, not inferred.

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