Get Entity

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the scope ('all properties') but does not disclose edge-case behavior such as what happens for an invalid handle, partial results, or performance implications. No contradiction exists, and the description adds modest behavioral context beyond the annotation.

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 no filler, front-loaded with the operation and target. It earns its place entirely; nothing could be removed without losing meaning.

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-only tool with an output schema present, the description covers the core need. The only notable gap is the lack of explicit error behavior for a nonexistent handle, but the output schema and annotations already carry much of the contextual load.

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 the only parameter 'handle' is fully documented in the schema. The description adds the phrase 'specific entity' but does not clarify handle format or lookup semantics, so value beyond schema is minimal — 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?

The description states a specific action ('Get') on a specific resource ('all properties of a specific entity' identified by handle). It clearly conveys the tool's function and is distinguishable from sibling tools like entity_list or analysis_entity_stats, though it does not explicitly name an alternative.

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 description implies the tool is used when you have a specific entity handle and need all its properties, and the readOnlyHint annotation confirms safe use. However, it provides no explicit when-to-use vs alternatives or exclusion criteria, leaving the agent to infer routing from context.

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