aleph_get_entity

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

Annotations already declare readOnlyHint and openWorldHint with destructiveHint false, covering safety. The description adds a concrete behavioral guarantee: the response includes every populated property, setting expectations for payload shape and completeness. No contradiction with 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?

Two concise sentences with the core action and scope front-loaded, followed by a single usage instruction. No filler or redundant restatement of the schema.

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 fetch tool with annotations covering safety and a clear usage hook, nothing essential is missing. There is no output schema, but the 'every populated property' phrase gives enough return-format expectation; invalid-ID behavior is not required for correct invocation.

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 parameter description 'Entity ID from a search result.' is already clear. The tool description reinforces that the ID comes from search results but adds no new format or semantics beyond the schema, so 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?

States a specific verb ('Fetch'), a precise resource ('one entity by ID'), and scope ('every populated property'). The 'Use after aleph_search' hook ties it to the search workflow and distinguishes it from sibling tools like aleph_search or aleph_expand_entity, so an agent can select it without opening the 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 says to use after aleph_search to see the full record behind a hit, which gives a clear context. It doesn't mention alternatives or when not to use it, but the workflow guidance is enough for a single-purpose fetch tool.

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