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

Annotations already declare it read-only, idempotent, and non-destructive. The description adds the 'paid' qualifier, which is a useful behavioral trait beyond annotations, but does not disclose other important behaviors like return format or error conditions.

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 very short and to the point, but it borders on under-specification. It is not verbose, but it lacks a full sentence and does not explain the tool's purpose sufficiently. The two pieces of information (topic and paid status) are useful, but the overall structure is minimal.

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?

Despite the simple parameter set and strong annotations, the description does not explain what data is returned or how to use the symbol parameter. The example in the schema provides some context, but the description alone is insufficient for a user to understand the tool's output or behavior.

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 schema has one required parameter 'symbol' with no description, and the description does not mention it at all. With schema coverage at 0%, the description was expected to compensate but provides no parameter semantics beyond the example in the schema.

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 identifies the resource (institutional ownership) and notes it is paid, but lacks an explicit verb like 'get' or 'retrieve'. It is more than a tautology and is distinguishable from sibling tools, but does not fully state the action performed.

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?

No guidance on when to use this tool or which alternatives might be better. The description only states the topic and that it is paid, with no mention of use cases or exclusions.

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