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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's burden is lighter. "Full record" usefully signals completeness relative to search results, but nothing is said about behavior when an id is unknown or stale, nor about permissions or rate limits.

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 sentence with the verb, scope, key parameter and provenance all front-loaded; there is no filler or redundant restatement of the tool name.

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 one-parameter read tool with readOnlyHint already declared and no output schema, this covers what an agent needs to invoke it correctly. The only material omission is the failure mode for an invalid or missing id, which matters slightly for a lookup tool.

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 0%, so the description must carry parameter meaning — and it does, explaining that id identifies a single result and originates from agentify_search, which is the most important semantic for this parameter. It does not specify the id format (opaque string vs UUID) or whether it must be exact, keeping it just short of full compensation.

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 ("Get the full record") plus a specific resource ("one Agentify result") scoped by id. The parenthetical naming agentify_search as the id source implicitly contrasts this single-record fetch with the sibling's search behavior, so the agent can tell them apart without opening a 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?

The phrase "(from agentify_search)" establishes the natural workflow — search first, then fetch by id — so usage is implied rather than stated. There is no explicit when-not guidance (e.g., that this should not be used to enumerate results, or that agentify_stats covers aggregate counts).

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