get_entity

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

With no annotations, the description carries the full burden. It usefully discloses that ambiguous matches are not selected (a fail-rather-than-guess behavior), but says nothing about permissions, error behavior, or what happens with the 'sections' parameter. The ambiguity note is genuinely valuable but incomplete.

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 sentence with the scope constraint front-loaded and no filler. It is efficient, though arguably too terse given the undocumented parameters.

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?

An output schema exists, so return values need not be explained, but with no annotations, three undocumented parameters, and zero required fields, the definition leaves too much unresolved for an agent to invoke it confidently.

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?

Three parameters with 0% schema description coverage, yet the description never mentions code, sections, or entity_id. It gives no indication of what identifiers are accepted, what 'sections' controls, or why nothing is required, so it fails to compensate for the coverage gap.

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: it retrieves the exact company or fund profile. It distinguishes the entity profile from siblings like get_financials, get_fund_portfolio, and get_disclosure, but does not name an alternative 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?

'Belirsiz eşleşmeyi seçmez' implies the tool requires an unambiguous identifier and will not resolve fuzzy matches, which hints that search_entities should be used when ambiguous. However, it never names that alternative or states prerequisites, leaving the routing to inference.

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