function

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds the block-table column format (`start size term successors`) and the 300-blocks-per-page pagination behavior, which are genuine behavioral details not in the annotations. It stops short of saying what happens at the end of a function with more than one page or how the paging interacts with callers/callees.

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?

Two sentences, both earning their place: the first defines content and pagination, the second routes to the alternative. Front-loaded with the resource and the notable format detail.

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?

No output schema exists, so the description must carry the return shape — it does so by enumerating the fact categories and the block-table columns, plus pagination. Minor gaps remain (total block count, behavior when a name resolves to multiple functions), but nothing essential to a correct call is missing.

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%, so both parameters are already documented — including the flexible "entry, any address inside it, or a name" semantics for address and the skip-count for offset. The description only restates the 300-per-page figure already present in the offset description, adding no new param-level meaning.

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?

Specific verb ("Show") plus resource ("one function") and an explicit inventory of the returned facts — range, counts, callers, callees, block table. It also names the sibling it is not, so an agent can distinguish it from function_summary without opening either schema.

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 states the negative condition ("Not for a readable triage") and names the alternative tool that should be used instead (function_summary). The positive case is implied by "raw facts", and the routing rule is unambiguous.

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