list_locations

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

With no annotations, the description must carry the burden of behavioral disclosure. It conveys a read-only 'List' operation, but does not explicitly state safety (non-destructive), return format, or any edge cases. The added context about LocationId is useful, but the description remains minimal and does not disclose beyond what the name implies.

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 two short sentences, front-loaded with the main purpose, followed by a practical use case. Every word earns its place with no fluff or repetition.

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 zero-parameter list tool, the description adequately explains what it does and why to call it, including a concrete downstream use. It lacks an explicit statement about return structure, but the mention of LocationId and the tool's simplicity make it sufficiently complete.

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 tool has zero parameters, so there is nothing to explain. Per rubric, 0 parameters yields a baseline of 4. The description does not need to add parameter meaning, and the empty schema is consistent.

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 clearly states 'List locations configured in the IntakeQ account.' This is a specific verb ('List') and resource ('locations'), and it distinguishes itself from sibling tools by targeting locations specifically, which no other sibling does.

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 explicitly says 'Call this before create_appointment to find a valid LocationId.' This provides clear when-to-use guidance and ties it to a specific downstream tool, making it highly actionable for an agent deciding when to invoke it.

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