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

With no annotations, the description carries the behavioral disclosure burden. It does disclose one notable behavior: concentration is reported when a single deal dominates a bucket, with a concrete illustrative example. However, it omits other useful behavioral traits such as time range, data granularity, or what the JSON response contains beyond a generic 200 note, so coverage is partial.

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 front-loaded with the core statement, then adds a useful distinction between sector and function, and a concrete example explaining the concentration behavior. The example is somewhat elaborate but earns its place by illustrating why concentration matters. It is concise enough for a human or agent to scan.

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?

The tool has no parameters, so input-side requirements are minimal, but there is no output schema and the description gives only a bare '200: Successful Response' line. It explains the conceptual classification and concentration caveat but does not specify what fields, aggregation, or format the JSON response will have. Acceptable for a report-style tool, but not fully complete.

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?

The input schema has zero parameters, so there are no parameter semantics to clarify. The description's conceptual context is irrelevant to parameter meaning, and the zero-parameter baseline of 4 applies.

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 opens with 'Capital by the business function it targets' and elaborates 'Where the money went, classified by whose job it changes.' This clearly identifies the resource (capital) and the classification dimension (business function), and distinguishes function labels from sector labels. It lacks an explicit verb like 'list' or 'report,' but the intent is unambiguous.

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 explains why function-based classification is actionable and explains concentration reporting, but it never tells an agent when to pick this tool over any of the many siblings. There is no 'use this when' or 'instead of X' guidance, leaving the selection entirely to inference from the name and subject matter.

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