createStakeholderMapSlide

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

The description only states 'create or update' without explaining the update mechanism (e.g., using _index). It does not disclose side effects, such as whether an existing slide is replaced or modified, nor any authorization or rate limit information. With no annotations, the description carries the full burden but fails to provide sufficient behavioral context.

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 extremely concise (one sentence), which is efficient, but it lacks necessary details to be fully useful. It sacrifices completeness for brevity.

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 tool has two parameters, one required, no output schema, and a complex nested structure, the description is too minimal. It does not explain how _index controls append vs update, what happens when stakeholders are provided, or what the tool returns.

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 description adds no meaning beyond the input schema. The schema already defines stakeholders with influence, interest, and name fields, and the description merely restates 'stakeholder influence-interest map.' With only 50% schema description coverage (missing description for the stakeholders array), the description does not compensate.

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 it creates or updates a stakeholder influence-interest map, which is a specific verb-resource combination. The name and description align, but it does not explicitly differentiate from sibling tools like createPositioningMap or createBcgMatrix, which are similar in concept.

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 on when to use this tool versus alternatives. The description does not mention contexts, prerequisites, or scenarios where a stakeholder map is appropriate compared to other slide creation tools.

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