get_resident_financial_activity_report

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

No annotations provided, so the description carries full burden. It only mentions the ID requirement and that it returns a report, but lacks details on read-only nature, pagination, idempotency, or rate limits. This is insufficient for a report tool.

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, first states purpose, second an important note. Concise but could be better structured (e.g., bullet points). No wasted words.

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?

With 6 parameters and no output schema, the description lacks explanation of filters, date range, boolean flag, and columns. It is incomplete for an agent to use effectively.

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 low (17%), and the description adds value by emphasizing the numeric string requirement for IDs, but does not explain other parameters like occurred_on_from, include_voided, or columns. Partially compensates but incomplete.

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 it returns a 'resident financial activity report' for given filters, distinguishing it from sibling reports like balance sheet or income statement by specifying 'resident financial activity', though it doesn't explicitly differentiate from similar financial reports like receivables activity.

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 provides a critical usage guideline: all ID parameters must be numeric strings, not names, and advises using directory reports to look up IDs. It lacks explicit when-to-use vs alternatives but implies context for resident financial data.

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