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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without description help. The description adds only scope-of-returned-data (entity/profile/user), and says nothing about auth requirements or what happens if no session exists. Adequate, not rich.

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 tight sentences that front-load the what before the why, with no filler. The second sentence is arguably redundant given the tool name, but it carries the only usage signal present.

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?

An output schema exists, so return-value structure need not be explained, and the description still summarizes the payload's content (entity, profile, user). For a zero-required-parameter read-only tool with rich annotations, an agent has everything needed to invoke it correctly.

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% with two enum-constrained, optional parameters ('fields' and 'format'), both fully documented in the schema. The description adds no parameter meaning beyond it, so the 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 and resource ('Get the full session info') and enumerates what the payload contains: active entity, profile, and user details. This makes it distinguishable in spirit from glpi_get_my_entities and glpi_get_my_profiles, though it never names those siblings as alternatives or clarifies the overlap.

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?

'Useful for debugging and verifying the current session context' gives a genuine, concrete use case rather than leaving usage implied. It stops short of exclusions or alternatives ('use X instead when...'), so it lands at clear-context-but-no-routing.

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