get_priorities

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

No annotations provided, and the description only includes 'GET /api/v1/priorities' and tags, which implies read-only behavior but does not disclose response format, authentication needs, or any other behavioral traits.

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?

Extremely concise with just two lines, front-loading the purpose. However, it could include a brief sentence on what the response contains without increasing length much.

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 parameterless GET endpoint, the description minimally explains the purpose but omits what the output looks like. Without an output schema, more context on return values would be helpful.

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 has no parameters with 100% coverage, so the description adds no parameter information. Baseline 3 is appropriate as no further detail is 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 states 'Get Conversation Priorities' which clearly identifies the verb (Get) and resource (Priorities), distinguishing it from sibling tools like 'update_conversation_priority' or 'get_statuses'.

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. Does not specify that it retrieves the list of available priorities, not conversation-level assignments.

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