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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states the tool 'retrieves' details, which implies a read operation, but it does not mention permissions, error handling (e.g., invalid ID), return format, or any side effects. For a tool with no structured safety hints, this is a significant gap.

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?

The description is concise at two sentences. The first sentence is packed with useful scope information, and the second adds the 'primary method' context. Every word earns its place, though the second sentence is slightly redundant with the first.

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?

With no output schema, the description should clarify what the tool returns, but it only says 'comprehensive details.' For a tool with 5 parameters and many sibling tools offering specific facets, the description gives a good overview but does not explain the response structure or how this tool differs in output from others. It is adequate but leaves gaps.

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?

The input schema has 100% coverage, so every parameter is already described (e.g., includeOwners, hierarchyDepth). The description adds a high-level context by mentioning 'ownership, hierarchies, and relationships,' which maps to the parameters, but it does not provide additional guidance on how to use the parameters or what valid values like 'full' mean beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool retrieves comprehensive details about a specific entity, listing metadata, ownership, hierarchies, and relationships. It uses a specific verb ('retrieve') and resource ('entity details'), and distinguishes it as the 'primary method' for complete information, though it does not explicitly contrast with siblings like getEntityDescriptor or getTeamDetails.

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 provides clear context by calling this the 'primary method' for getting complete information, implying it is the go-to tool for full entity details. However, it does not explicitly state when not to use it or mention any alternative tools, so it falls short of the full 5.

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