youfiliate_list_smart_links

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description reinforces idempotence by stating 'Does NOT create or modify any links' and adds pagination context. No new behavioral traits are disclosed beyond annotations, but consistency is maintained.

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?

The description is concise with a clear front-loaded purpose, bullet-style argument listing, and a helpful common errors section. Every sentence adds value without redundancy.

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?

The description covers the main functionality, pagination, filtering, and a common error. With an output schema present, return type details are not needed. However, it could mention that results can be formatted as markdown or json based on response_format parameter.

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 description lists key filters (health_status, search, ordering, limit, offset) but misses response_format. The input schema provides detailed descriptions for all nested parameters, so the description adds a concise summary but does not significantly enhance meaning beyond 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?

The description clearly states the tool lists smart links with optional filters and pagination. It explicitly says 'Does NOT create or modify any links,' distinguishing it from sibling tools like create_smart_link and update_smart_link.

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 filtering and searching links but does not explicitly guide when to use this tool over alternatives like get_smart_link or other list tools. The common error note provides some context but lacks explicit when-to-use/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.