Find Or Create Location(S) By Path

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description confirms creation but does not explain what happens when a location already exists (presumably returns it). It also incorrectly mentions 'Creates a new Project records' which is misleading. Minimal behavioral disclosure beyond 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 three sentences and includes redundant information like the API endpoint and method. It could be more concise, and the typo 'Project records' wastes space. Adequate but not excellent.

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?

No output schema exists, so the description should explain return values. It only mentions returns on success for creation (HTTP 201), not for retrieval. It also does not cover edge cases like path not found or multiple locations. Incomplete.

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 covers both parameters with descriptions (100% coverage). The description lists required parameters but adds no additional meaning. It mentions 'path' as an array of Location names but this is already in the schema. Baseline 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 states the tool retrieves or creates Location(s) by path, which is clear. However, it contains a typo: 'perform the find or action' and incorrectly mentions 'Creates a new Project records' instead of Location records, which could confuse an AI agent.

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 says 'Use this to perform the find or action on Project records' but does not explain when to use this tool versus alternatives like 'create_location' or 'list_locations'. No exclusions or prerequisites are provided.

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