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 only says it is 'leftover' and 'same as search_tickets with status=open', which gives no information about side effects (e.g., whether it is read-only or mutating), authentication requirements, rate limits, or any other runtime behavior. It does not disclose any behavioral traits beyond what the description itself says, and the term 'leftover' is unhelpful.

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 short, which could be seen as concise, but it is under-specification rather than deliberate conciseness. It does not front-load any useful information; it simply labels the tool as 'leftover' and refers to another tool. Every sentence does not earn its place because the content is not informative.

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 has a parameter, no annotations, and no output schema, the description is completely inadequate. An agent cannot determine what the tool returns, how to interpret the 'limit' parameter, or what 'tasks' are in this context. The reference to search_tickets is insufficient without details on the response structure or usage conditions.

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 schema has one parameter, 'limit', which has no description in the schema (0% coverage) and the description does not explain its meaning or purpose. The description does not add any value to the schema; it fails to compensate for the lack of schema documentation, leaving the parameter semantically empty.

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 that the tool is a leftover and equivalent to search_tickets with status=open, which identifies the resource and a filter condition, but it does not clearly state what the tool actually does (e.g., lists or retrieves tasks). The purpose is vague and relies heavily on referencing another tool.

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. It only mentions that it is a leftover and same as search_tickets with status=open, but that reference is to a sibling tool, not a clear instruction for use. It does not explain why an agent would choose this over search_tickets or any other sibling.

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