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

No behavioral information is provided beyond the tautological description. With no annotations and no output schema, an agent cannot tell whether this tool performs a simple calculation, calls an external API, or has side effects.

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 extremely short, but this is under-specification rather than effective conciseness. The repetition of 'Dividend Yield' adds no value. A useful description would state the tool computes or retrieves the dividend yield percentage for a given security.

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 has zero context about how the tool works, how an agent should call it, or what response to expect. For a finance-related tool, it is not even clear whether the agent needs to supply a ticker symbol, though the schema has no parameters. The description is wholly inadequate compared to the rich sibling set.

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 for the description to clarify. The schema coverage is 100% by default since there is nothing to document. A baseline of 4 is appropriate because the description does not need to compensate for missing parameter documentation.

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 is a tautology: 'Dividend Yield: Dividend Yield' merely repeats the tool name. It fails to state what the tool actually does, what inputs it expects, or what output it produces. The name suggests a finance function, but the description does not clarify whether it calculates, fetches, or formats dividend yield data.

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 no guidance on when to use this tool versus alternatives. There is no indication of use cases, prerequisites, or context. Among hundreds of sibling tools, this is particularly unhelpful.

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