list_compositions

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

With no annotations provided, the description carries the full burden for behavioral disclosure. 'List all compositions' clearly indicates a non-mutating read operation, and 'in the project' scopes the action. It does not explicitly confirm absence of side effects or describe return details, but the wording is sufficiently transparent for a zero-parameter list operation.

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 one short, front-loaded sentence with no filler, repetition, or unnecessary detail. Every word carries meaning, and it is minimally sufficient for the tool's zero-parameter nature.

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 zero-parameter list tool, the description is quite complete, but it could be more explicit about returning an array or which project is considered 'the project' (e.g., the currently open project). Without an output schema, a slight clarification about the return value would close the remaining gap.

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 no parameter semantics to document. The schema description coverage is trivially 100%, and the description adds enough context with 'all compositions in the project' even though it cannot elaborate on nonexistent parameters.

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 uses a specific verb ('List'), identifies the resource ('compositions'), and states the scope ('in the project'). It clearly differentiates from sibling tools like get_composition_info, create_composition, and delete_composition, which are for individual or state-changing operations.

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 implies the tool is for retrieving an overview of all compositions in the project, but it does not state explicit when-to-use or compare with alternatives. Sibling tools like get_composition_info provide contrast, but no direct guidance or exclusion is given.

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