Session Locations

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds value by disclosing the actual output shape (latitude, longitude, city, country, session count), which is especially useful given no output schema. It doesn't cover defaults like date ranges or pagination behavior, but the safety profile is already handled by 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?

A single sentence that front-loads the verb and resource, immediately states the return fields, and ends with the intended use case. Every clause contributes meaning, with no redundant filler.

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 read-only data-fetching tool with a complete parameter schema and supportive annotations, the description provides enough to select and invoke it correctly. It lacks details on default date windows or pagination behavior, which would be helpful given no output schema, but the core purpose, return values, and use case are present.

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 input schema fully documents all 9 parameters. The description does not add parameter-level detail, which is acceptable given the schema's completeness. Baseline 3 applies because no param semantics beyond the schema are needed.

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 opens with a specific verb and resource: 'Get geographic session location data with coordinates.' It also lists the concrete return fields (latitude, longitude, city, country, session count), making it easy to distinguish from sibling session tools like list_sessions and get_session.

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 clearly frames when the tool is appropriate: 'for map visualization and geographic analysis.' It does not explicitly name alternatives or exclusion conditions, but the use case is specific enough that an agent can infer this is the geo-focused session data tool among many siblings.

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