getAcquisitionOwnership

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

Annotations (readOnlyHint=true, idempotentHint=true) already disclose core safety and idempotency. The description adds context about the kind of data but does not discuss additional behaviors like pagination, rate limits, or response structure, which could be expected for a data retrieval 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 concise sentences front-load the purpose and scope. No filler, but could be slightly sharper by eliminating the redundant 'Acquisition Ownership API' mention.

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 description explains the tool's domain and purpose but omits output details (e.g., fields returned), which is notable given the lack of an output schema. For a simple tool with strong annotations, it is adequate but not comprehensive.

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?

With 100% schema coverage, the schema already describes both parameters (symbol and limit). The description does not add extra meaning beyond the schema, so it meets the baseline without compensating for any gaps.

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 uses a specific verb ('Track changes') and resource ('stock ownership during acquisitions'), clearly distinguishing this tool from siblings like getLatestMergersAcquisitions which likely list M&A events rather than ownership impacts.

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 implies usage for tracking ownership changes in acquisitions but provides no explicit guidance on when to use this tool vs. alternatives like searchMergersAcquisitions or getLatestMergersAcquisitions, nor does it mention exclusions or prerequisites.

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