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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds the useful framing 'Facts, not accusations' and lists returned fields, but does not disclose deeper behavioral details such as freshness, limitations, or pagination.

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 compact and front-loaded, defining the resource first and then clarifying scope. Every sentence contributes without unnecessary repetition.

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 and annotations carry much of the structural burden, and the description supplies the conceptual definition and ticker/market scope. It is nearly complete, though it does not mention the time-window parameter or result limits explicitly.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description only reinforces the ticker scope and does not add meaning for days or limit beyond what the schema provides.

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 defines the specific resource: people who moved from government jobs into lobbying, including the data fields returned. It is more specific than the name alone, but it does not explicitly differentiate this from sibling tools such as list_corporate_lobbying.

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?

It states the tool can be used 'By ticker or across the market,' which clarifies optional ticker usage. However, it gives no explicit guidance on when to choose this tool versus alternatives like list_corporate_lobbying or list_congress_trades.

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