odp_get_transactions

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

No annotations are provided, so the description must carry the full burden. While 'get' implies a read operation, the description does not disclose any behavioral traits such as idempotency, safety, rate limits, or potential side effects. This is a significant gap.

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 two sentences plus an args block. The usage guidance is front-loaded, and no words are wasted. Every sentence serves a purpose.

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 the tool's simplicity (one parameter, likely read-only), the description covers purpose and usage well. An output schema exists, so return values are documented elsewhere. However, it lacks any behavioral or prerequisites context, slightly reducing completeness.

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 0%, but the description adds an 'Args' section explaining the single parameter 'app_num' as 'Application number without slashes' with an example. This provides meaningful format guidance beyond the schema's bare type definition.

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 retrieves 'prosecution transaction history for an application'. The verb 'get' and resource 'transactions' are specific and distinguish it from sibling tools like odp_get_application or odp_get_documents.

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 includes a 'USE THIS TOOL WHEN' section that specifies the use case: 'complete timeline of prosecution events including office actions, responses, and fee payments'. This provides clear context, but does not explicitly list when not to use or mention alternatives.

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