org_endpoint_publisher_os_locate_position

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

No annotations are provided, so the description carries full responsibility. It claims 'Returns events' but does not disclose side effects, permissions, or idempotency. Moreover, it states that q and positionQuery are required, contradicting the schema which marks them as optional with default null. This misrepresentation undermines transparency.

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 very short (one line) but includes redundant information (the endpoint path is essentially the tool name). It is not well-structured, mixing path and usage notes. While not overly verbose, it sacrifices clarity for brevity.

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?

Given three parameters, no output schema, and no annotations, the description is incomplete. It fails to explain what 'locate position' returns, how the parameters affect behavior, or expected output format. An agent would lack critical context to use this tool 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?

The schema already describes all parameters (100% coverage). The description adds only the misleading claim that q and positionQuery are required, which contradicts the schema. No useful semantic context is added; instead, it introduces error.

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 merely restates the endpoint path and says 'Returns events,' but it does not clearly explain what 'locate position' means or how it differs from sibling tools like 'organization_publisher_operating_systems_locate_object_position' or search tools. The purpose is vague and not differentiated.

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?

No guidance is given on when to use this tool versus alternatives. The description mentions required parameters but does not explain scenarios for invocation. Siblings exist with similar names, but no when-to-use or when-not-to-use context is provided.

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