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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: it specifies that turnover is computed between the two most recent loaded quarters, and that sector data is intentionally omitted rather than fabricated. This is valuable context the annotations do not provide.

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 three sentences: what the profile contains, when to use it, and what it deliberately excludes. Each sentence earns its place with no filler or 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?

For a single-parameter read-only tool with no output schema, the description names the key data points returned, gives a concrete use case, and discloses a data limitation. It does not describe behavior for ambiguous or unmatched manager names, but for this tool's simplicity the coverage is strong.

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%, and the schema already describes the single parameter as a filing manager name or distinctive fragment. The description adds no additional parameter-level detail, so the baseline score of 3 is appropriate.

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 what the tool produces: a 13F profile with portfolio concentration, turnover, and top positions. It also explicitly notes what it excludes (sector/industry exposure). However, it lacks an explicit verb like 'Get' or 'Show,' and it does not name sibling tools to draw a direct contrast, so an agent must infer the differentiation.

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 gives a concrete use case: characterize a manager's style before targeting them, e.g., for a newsletter. It also states a clear exclusion ('Does NOT include sector/industry exposure') and explains why. It does not, however, name an alternative tool to use when sector exposure is needed, so the when-not-to-use guidance is incomplete.

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