list_salutations

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds no additional behavioral context such as pagination behavior, default limit, or relationship to other outputs; it simply restates the list action without enriching the agent's understanding.

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 a single, compact sentence with no unnecessary text. It is appropriately sized for a simple list operation and front-loads the essential verb and object.

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 list tool with good annotations and schema coverage, the description is minimally adequate. However, it lacks any usage guidance, such as distinguishing when to use this vs 'search_salutations', and does not mention any caveats about the returned data. This is a clear gap for a tool that could potentially be confused with a search variant.

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 descriptions cover 100% of parameters, with clear descriptions for 'limit' (max 2000) and 'offset' (skip over elements). The tool description does not add any extra meaning about parameters beyond the schema, so it meets the baseline expected for full schema coverage.

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 'Fetch a list of salutations' clearly identifies the action (fetch) and resource (salutations), making the tool's purpose obvious. However, it does not differentiate from sibling tools like 'search_salutations' or provide any scope details such as whether it returns all salutations or paginated results.

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 no guidance on when to use this tool versus alternatives like 'search_salutations' or 'get_salutation'. There is no mention of use cases, exclusions, prerequisites, or scenarios where a different tool would be more appropriate.

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