list_figures_v1_figures_get

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

No annotations provided, so description carries full burden. It discloses GET method, public access, auth not required, sort orders, and result fields. Minor omission: no mention of pagination details beyond 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?

Five concise sentences, each adding distinct information: route, purpose, definition, results, sort options, auth status. No redundancy; front-loaded with key info.

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?

Defines figures, lists output fields, explains sorts, and notes public access. Lacks default sort order (optional param) but schema covers optionality. Good for a list tool with schema but no output schema.

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 100% with descriptions. Description adds value by detailing sort order logic (like_count DESC, created_at DESC) beyond schema's brief descriptions. Limit and offset not elaborated but schema suffices.

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 clearly states the tool lists public figures for the discovery feed, defines what a figure is, and mentions included fields. It distinguishes from siblings like list_user_figures by specifying 'public' and 'discovery feed'.

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?

The description implies usage for the discovery feed and notes no authentication, but does not explicitly tell when to use this versus alternatives (e.g., list_user_figures). No when-not-to-use guidance.

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