threads_get_user_threads

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

No annotations provided, and description is sparse: it does not disclose read-only nature, pagination behavior, auth needs, or any side effects. The alias mention adds some context but fails to cover essential behavioral traits.

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?

Single sentence, extremely concise and front-loaded. Could include a bit more detail without becoming verbose, but efficient.

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?

No output schema and no annotations; description only states alias. Lacks information on return values, pagination behavior, or usage details, leaving significant gaps for agent understanding.

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 100% and descriptions adequately explain parameters. Description adds no extra parameter info beyond schema, meeting baseline.

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?

Description clearly states verb (Get), resource (all threads published by user), and explicitly calls out as alias for threads_get_posts with user context, distinguishing it from sibling.

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 it's an alias for threads_get_posts with user context, giving clear context for when to use this vs sibling. No explicit exclusions but provides sufficient guidance.

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