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

Annotations already declare readOnlyHint and idempotentHint, covering safety and idempotency. The description adds a small but useful behavioral detail: the 'current' scope of the POI. However, it does not explain what POI stands for, how the current POI is determined, or what details are returned, so it adds limited behavioral context beyond the 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?

The description is a single, front-loaded sentence with no wasted words. It clearly communicates the tool's purpose in minimal space, earning a perfect score for conciseness.

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 simple one-parameter getter with annotations covering safety, the description is adequate. It states exactly what the tool retrieves ('your current POI details'). While it doesn't describe the return format or what constitutes a POI, the tool's simplicity makes this less critical. The presence of many siblings slightly increases the need for clarification, but overall the description is complete enough.

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 only parameter session_id is fully described in the schema ('Your session ID from login/register'), so schema coverage is 100%. The tool description doesn't add any parameter-specific meaning beyond what the schema already provides, hence the baseline score of 3.

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 uses the specific verb 'Get' and names the resource 'your current POI details', clearly indicating a read operation. It is concise and distinguishes itself from many get_* siblings by focusing on the user's current POI, though it doesn't explicitly contrast with related tools like get_nearby or get_map.

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 no guidance on when to use this tool versus alternatives. It only states what the tool does, without mentioning any context, prerequisites, or exclusions. Given the large sibling list, some usage guidance would be expected.

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