conduyt_remove_dashboard_tile

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

With no annotations, the description must carry the safety profile. It does disclose the key side effect (the saved report is retained), which is genuinely useful. It does not say whether tile removal is reversible, what permissions are required, or what the response contains.

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?

One short sentence, front-loaded with the action, with the clarifying parenthetical placed exactly where it prevents a misread. No waste.

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?

A simple two-parameter tool with no output schema, so the description does not need to explain return values. However, with zero annotations and an undocumented required parameter, an agent still lacks confirmation of reversibility and the origin of tileId.

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 only 50% — id is documented as "Dashboard id" but tileId has no description at all. The tool description says nothing about either parameter, so it fails to compensate for the undocumented tileId and adds no meaning over the schema.

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?

States a specific verb ("Remove") and resource ("a tile from a dashboard"), which cleanly separates it from add_dashboard_tile, update_dashboard_tile, and delete_dashboard. An agent can pick it out of the dashboard tool family from the name plus description alone.

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 parenthetical ("the saved report stays") implies when this is appropriate — when you want to declutter a dashboard without deleting the underlying report — but no alternative tool is named and no precondition (e.g., needing the tile id from get_dashboard) is stated. Usage is inferable rather than explicit.

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