get_public_dashboard_tile

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

With no annotations provided, the description carries full burden. It only states what the tool does (get a map tile) but does not disclose return format, whether authentication is needed (though public likely implies none), rate limits, or any side effects. This is insufficient for a tool with no annotation coverage.

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, short sentence that is concise and front-loaded. However, it is too brief for the tool's complexity, omitting critical details. It earns a middle score for being to the point but lacking necessary substance.

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 complexity (nested object, 6 parameters, no output schema, no annotations), the description is incomplete. It does not explain the output (e.g., image URL or binary), parameter roles, or any prerequisites like the need for an existing public dashboard.

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 6 parameters with 0% description coverage. The description adds no explanations for any parameter, leaving the agent to guess the meaning of 'zoom', 'x', 'y', etc. Without schema descriptions or clarifying text, the agent cannot correctly select values.

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 specifies the verb 'Get', the resource 'map tile', and the source 'public dashboard dashcard'. It effectively distinguishes itself from sibling tools like get_dashboard_tile (non-public) and get_public_card_tile (for cards, not dashcards).

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, no prerequisites, and no context on when not to use it. It is missing any usage recommendations.

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