plu_get_messages

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

No annotations are provided, and the description only says "Get messages," implicitly indicating a read operation. It does not disclose any other behavioral traits such as read-only nature, data limits, or error behavior, leaving the burden unmet.

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 extremely concise with one sentence, but it is under-specified and lacks structure. It does not earn its place due to missing critical information.

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?

The description is incomplete for a tool with two required parameters, no output schema, and no annotations. It fails to explain what constitutes a thread, what the parameters represent, or what the response format is.

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 description does not mention or explain the parameters (userId, propertyId) at all. With 0% schema description coverage, the description fails to add any meaning beyond what the schema provides.

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 messages in a thread," which specifies the action and resource. However, the parameters are userId and propertyId, not threadId, and there is a sibling tool plu_get_conversations, making the purpose ambiguous and not clearly 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 like plu_get_conversations or plu_send_message. The description does not provide any context for appropriate usage.

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