createKpiHighlightSlide

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

No annotations exist, so the description must fully disclose behavior. It only mentions 'create or update' without explaining what happens during update (e.g., overwrite fields, append, behavior with _index). The _index parameter's role is hinted in its schema but not in the description.

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 very short (one sentence) and front-loads the purpose, but it is too terse to be fully informative. It lacks structure or breakdown of key details.

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 of 3 parameters, no output schema, and many sibling tools, the description is insufficient. It does not explain return values, update mechanics, or provide enough context for an agent to use it correctly among dozens of similar tools.

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 description coverage is only 33% (_index has a description). The description adds no information about 'kpis' or 'title' beyond their names. The schema shows kpis is an array of objects with label, value, delta, but the description does not elaborate on their purpose or format.

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 'Create or update a slide highlighting key KPIs,' which identifies the verb (create/update) and resource (KPI highlight slide). However, it does not distinguish this from sibling tools like createOkrKpiDashboardSlide or createExecutiveSummarySlide, which may also involve KPIs.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling slide creation tools, the absence of usage criteria or context makes it hard for an agent to choose correctly.

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