search_find_unused_entities

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

No annotations are provided, so the description should disclose behavioral traits such as read-only status or side effects. The description only states it is a 'heuristic' and gives the criteria, but does not clarify if it is safe to call repeatedly or if it modifies state.

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, clear sentence that is front-loaded with the purpose ('Heuristic: entities that look unused') and provides specific criteria. Every word adds value.

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?

The tool has 0 parameters and an output schema, so the description doesn't need to explain return values. However, it lacks context about side effects, permissions, or when to prefer this over sibling tools. Given the complexity of the domain, this is a notable 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 input schema has 0 parameters with high schema coverage, so the baseline is 4. The description adds no parameter info, but none is needed. The description appropriately explains what the tool does without 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 clearly states the tool finds unused entities based on specific heuristic criteria: unavailable/unknown for >7 days or orphan with no device. It distinguishes from sibling tools like search_find_orphan_devices (devices, not entities) and search_deep_search.

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_find_orphan_devices or search_deep_search. It does not mention prerequisites, limitations, or exclusions.

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