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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: parallel per-property CSV downloads and the company-wide fallback when no portfolio/property_ids are supplied. No rate-limit or output-shape notes, but the output schema exists.

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?

Three short, front-loaded sentences with no filler; the resource definition leads and the scoping rule follows. Efficient, though the parenthetical acronym breakdown is minor padding.

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?

An output schema exists so return values need not be described. The description covers the read-only analysis, its data source and its scoping behavior adequately; only the show_detail flag and property_ids format remain undocumented.

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 0% for 4 parameters, so the description must compensate. It implicitly covers as_of_date ('as of a date'), portfolio and property_ids (via the company-wide default sentence), but says nothing about show_detail or the expected format of property_ids, leaving one parameter and one format question unanswered.

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?

States a specific verb and resource ('Downloads BalanceSheet (report 38) CSVs') with a clear scope qualifier ('as of a date', 'per property' vs 'company-wide'). The resource name distinguishes it from the many analyze_* financial siblings, but it never explicitly contrasts itself with adjacent tools such as analyze_financials or trial_balance.

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?

'With no portfolio/property_ids, pulls the company-wide balance sheet' tells the agent what happens by default, which is useful implied guidance. It does not state when to prefer this tool over analyze_financials/trial_balance or any explicit exclusions, so guidance remains implicit.

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