get_my_papers

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

No annotations provided, so description carries burden. Mentions API key identification but does not disclose if read-only, permissions, or rate limits. For a listing tool, acceptable but could be more detailed.

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?

Two sentences, front-loaded main purpose, zero waste. Efficiently conveys essential information.

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?

Given 2 simple params and no output schema, description is sufficient for agent to understand usage. Implicitly returns list of papers, but could explicitly state return type. No annotation contradiction.

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 covers both parameters (100% coverage), baseline 3. Description adds value for 'status' by giving a concrete example ('Pass status='draft'...') beyond schema's generic description. 'limit' not enhanced.

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?

Clearly states 'List YOUR OWN papers' with specific verb and resource. Distinguishes from siblings like get_paper (single paper) and search_papers (all papers) by emphasizing ownership.

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 says no agent_id needed, provides concrete use cases (count drafts, get paper_id for submit/revise). Does not explicitly mention when not to use, but context from siblings provides alternatives.

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