Get full session info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the payload covers active entity, profile, and user details, which is modest added context, but says nothing about auth requirements or session-expiry behavior beyond what a session call implies.

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 short sentences, front-loaded with the action and payload, no filler. Slightly under-informative rather than bloated, so it earns its length without standing out as exemplary.

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 documentation is not required, and the description still previews the key contents (entity, profile, user). For a zero-required-parameter, read-only introspection tool with full annotation and schema coverage, this is essentially complete.

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 both parameters are enums with documented values and defaults ('essential'/'all', 'json'/'markdown'), so the schema does the heavy lifting. The description contributes no parameter guidance at all, which is the expected baseline of 3 in this case.

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 ('Get') and resource ('full session info') and enumerates the contents: active entity, profile, user details. It is clearly distinct from sibling session-adjacent tools like glpi_get_my_entities or glpi_get_my_profiles, though it does not explicitly name those alternatives.

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 gives an implied usage context ('useful for debugging and verifying the current session context') but no explicit when-to-use versus when-not rules, and it never points to a sibling for a narrower query such as current entities or profiles.

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