dashboards_remove_dashboard_resource

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

With no annotations, the description carries the burden. It indicates destructive action via 'Remove' and a safety mechanism with confirm flag. However, it does not discuss side effects, irreversibility, or authentication requirements, which are moderately important for a deletion tool.

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?

Two sentences with no filler. The first sentence states the core purpose, and the second gives actionable advice. Every word 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?

For a simple tool with few parameters and an existing output schema, the description covers the essential action and usage hints. It lacks mention of return value or error handling, but the output schema likely covers that. Sibling tools provide context.

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 coverage is 0%, so the description must compensate. It adds meaning to resource_id ('numeric ID') and confirm ('to proceed'), but does not explain data types or constraints beyond the schema. The description provides basic clarification but not deep semantics.

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 verb 'Remove' and the resource 'Lovelace resource', specifying 'by its numeric ID'. It distinguishes itself from sibling tools like dashboards_add_dashboard_resource and dashboards_update_dashboard_resource by being the removal counterpart.

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 concrete usage guidance: 'Set confirm=True to proceed' and 'Use get_dashboard_resources() to find the resource ID'. It does not explicitly state when not to use, but it is clear enough for an agent to understand the action and prerequisites.

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