get_stock_server

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds only the endpoint mapping '(stocks/show)' and says nothing about return shape, error behavior, or access requirements, so it contributes little beyond the annotations.

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?

A single compact fragment that is front-loaded with the essential information and contains no filler. It is efficient, though the endpoint parenthetical is marginally useful to an agent.

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 lookup with full schema coverage and no output schema, the description is minimally adequate. It omits any routing to the list tool or hint about what 'details' includes, leaving a modest gap for an agent deciding between it and list_stock_servers.

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 description coverage is 100% and the single 'id' parameter is fully documented in the schema ('Stock server ID from list_stock_servers'). The description adds no further semantics about the identifier, so the baseline 3 applies.

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 states a specific resource (a specific stock server) and an operation (retrieve details), and the parenthetical '(stocks/show)' pins the underlying endpoint. It implies the singular counterpart to list_stock_servers, but never names that sibling explicitly, so differentiation relies on inference.

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 statement of when to use this tool versus list_stock_servers or any other retrieval sibling, and no prerequisites or exclusions. Usage can only be inferred from the phrase 'a specific stock server' and the schema note that the id comes from list_stock_servers.

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