ptero_app_get_locations

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

No annotations provided, and the description only repeats the HTTP method and path. It discloses no behavioral traits like authentication, rate limits, or side effects.

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 concise but at the expense of completeness. It is essentially just the endpoint path, omitting any context or explanation.

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?

With no annotations, no output schema, and undocumented parameters, the description is grossly incomplete. It provides minimal information for the agent to correctly invoke the tool.

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 input schema defines two parameters (query and body) with no documentation, and the description adds no meaning. Schema description coverage is 0%, so the agent gets no help understanding parameter usage.

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 specifies 'GET /api/application/locations', indicating a read operation on locations. However, it does not clarify whether it lists all locations or has other semantics, nor does it distinguish from sibling tools like ptero_app_get_locations_location.

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 on when to use this tool versus alternatives such as ptero_app_get_locations_location or ptero_app_get_nodes. The agent receives no context for selection.

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