get_messages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering capability but lacks critical information: it doesn't specify whether this is a read-only operation (implied but not stated), what authentication is required, whether there are rate limits, what the return format looks like, or if there's pagination for large result sets. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 just two sentences that directly address the tool's purpose and main optional feature. Every word earns its place with zero redundancy. The structure is front-loaded with the primary purpose followed by the filtering capability.

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?

Given the tool's moderate complexity (retrieving message threads with optional filtering), no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'message threads' contain, how results are structured, whether authentication is needed, or any error conditions. For a data retrieval tool without structured output documentation, the description should provide more context about what the agent can expect.

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 description coverage is 100%, so the schema already documents the single optional parameter 'sitterId' with its description. The description adds minimal value by mentioning 'Optionally filter by sitter ID' which essentially repeats what the schema provides. No additional semantic context about parameter usage or constraints is provided beyond the structured schema.

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 the tool's purpose: 'Get your message threads on Rover' specifies the verb (get) and resource (message threads). It distinguishes from siblings like 'message_sitter' (which sends messages) and 'get_bookings' (which retrieves bookings). However, it doesn't explicitly differentiate from potential message-related tools that might exist in other contexts.

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 provides implied usage guidance by mentioning the optional sitter ID filter, suggesting this tool is for retrieving existing message threads rather than creating new ones. However, it doesn't explicitly state when to use this versus alternatives like 'message_sitter' (for sending) or provide clear exclusion criteria (e.g., when not to use it for new conversations).

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