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

The readOnlyHint annotation already establishes the safe read-only nature. The description adds meaningful behavioral context by stating that the response indicates whether the price is from market close or from an intraday quote, which helps set expectations for data source and timing.

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 a single focused sentence that conveys the essential purpose and output nuance without any filler. It is front-loaded with the core action and keeps the added detail about quote source tight.

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 simple read-only tool with one parameter and no output schema, the description covers the main return characteristics: current price and its origin. It falls short only in not specifying symbol format or currency, but the low complexity makes the definition reasonably 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 schema provides only the parameter name 'symbol' with no description, and the description does not elaborate on the expected format, exchange, or uniqueness of the symbol. The phrase 'jednej spółki' offers minimal context that the value identifies a single company, but it is still mostly left to inference.

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 identifies a single-company spot price lookup and adds the key distinction of whether the price comes from the close or an intraday session quote. This is specific enough to separate it from siblings like get_price_series and get_intraday_quote, though it does not name them explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as get_intraday_quote or get_price_series. The description states what it returns but not the conditions that would make it the preferred choice.

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