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

With no annotations, the description carries the full burden, and it does disclose the 5-match cap and the returned fields (name, symbol/isin, totalShortPct, website). It says nothing about permissions, error/empty-result behavior, or whether there is any way to page past the 5-match limit, which matters for a search tool agents may rely on for disambiguation.

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?

Three short sentences: what it finds, what comes back including the cap, and what to do next. Zero filler and the actionable routing is front-and-center.

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 single-parameter lookup with no output schema, the description supplies the return shape and the match limit, which is exactly what is missing from structured fields. It could note behavior on zero matches or point to sibling alternatives when the entity is already known.

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 coverage is 100% and the single parameter is self-documenting, so the baseline 3 applies. The description restates the accepted key types but adds no format guidance (e.g., ISIN casing rules) beyond 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?

States a specific verb and resource ('Find companies with published short positions') and immediately scopes the lookup keys (name, ticker, ISIN). It also names the sibling it hands off to, so an agent can distinguish it from the other get_* retrieval tools.

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?

Explicitly routes the agent forward: 'Pass the returned symbol or isin to get_company_short_positions.' That makes the search-then-fetch workflow clear. It stops short of stating when NOT to use this tool (e.g., when the symbol is already known), so 4 rather than 5.

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