Get Politician P&L

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

Discloses that figures are estimates with ±25-40% error, details the FIFO and mark-to-market methodology, and matches the readOnlyHint annotation. No contradictions.

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 somewhat long but well-structured, front-loading purpose and methodology, then explaining output and accuracy. Every sentence adds value.

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 complexity, the description covers methodology, output structure, and accuracy. The output schema exists, so the description's overview is sufficient. Minor gap: no explicit mention of pagination or limits.

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%, so baseline is 3. The description adds context about slug format and prerequisite, but the schema already includes a detailed description of the slug parameter.

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 estimated P&L for a politician, with specific resource and action. It mentions scope (Congress and executive branch) but does not explicitly differentiate from sibling tools like get_politician_activity or get_politician_transactions.

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?

Provides explicit prerequisite: 'Use get_politicians first to find the slug.' Also explains methodology and accuracy caveats, helping the agent decide when to use this tool. Lacks explicit when-not-to-use conditions.

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