odp_get_application

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

No annotations provided; description implies read-only behavior ('get'), but doesn't explicitly state safety, authorization needs, or rate limits. For a simple read tool, basic transparency is met but could be stronger.

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?

Well-structured with clear sections (USE THIS TOOL WHEN, Args, Returns). Concise without redundancy, though the Returns section is somewhat generic. Overall 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?

Output schema exists, so detailed return specs aren't needed. Description covers key return fields (filing date, status, basic info) and parameter usage. No significant gaps for a simple data retrieval 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?

Single parameter app_num is thoroughly described: format 'without slashes or commas' with an example '14412875'. Schema coverage is 0%, so description fully compensates and adds essential formatting guidance.

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 the tool retrieves patent application data from USPTO Open Data Portal, specifying 'prosecution/file wrapper data including status, dates, and basic metadata.' This distinguishes it from siblings like odp_get_application_metadata, which presumably returns only metadata.

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?

Explicit 'USE THIS TOOL WHEN:' section identifies the use case: needing prosecution/file wrapper data. Context hints at when not to use (e.g., for metadata only), but doesn't explicitly name alternatives.

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