list_magic_dash

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

With no annotations provided, the description must disclose behavioral traits. 'Retrieve' implies a non-destructive operation, but there is no mention of pagination, filtering behavior, authentication needs, or the structure of the returned items. The description adds minimal transparency beyond the verb itself.

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, front-loaded sentence that efficiently conveys the basic purpose. It avoids redundancy and verbosity, but it is so terse that it borders on under-specification; still, as a concise summary, it earns its place.

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 four parameters, no annotations, and no output schema, the description is highly incomplete. It does not explain what a Magic Dash Item is, how pagination works, or what type of data is returned, leaving significant gaps for an agent trying to invoke the tool correctly.

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 input schema contains four parameters (page, title, page_size, company_id) with 0% schema description coverage, and the description does not mention any of them. It fails to explain how these parameters affect the result, leaving the agent without essential information about filtering or pagination.

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 a clear action ('Retrieve') and a specific resource ('Magic Dash Items'), making the tool's primary purpose understandable. However, it lacks differentiation from sibling list tools beyond the unique entity name, and the term 'Magic Dash Items' is not defined, so the scope remains somewhat vague.

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?

There is no guidance about when to use this tool versus alternatives like list_lists or other list_* tools. The description merely states what it does without mentioning prerequisites, exclusions, or recommended usage contexts.

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