createPartnershipMapSlide

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

With no annotations, the description must carry the burden, but it only states 'create or update' without disclosing side effects, permissions, or how updates are identified. The _index parameter behavior is described in the schema, but the description adds no further 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 very concise (one sentence), which aids readability, but it is too brief and lacks front-loaded critical details like the dual create/update capability. It could be restructured to be more informative without extra length.

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's complexity (3 params, many siblings, no output schema), the description is inadequate. It does not explain what a partnership ecosystem map is, how slides are organized, or what the return value is, making it hard for the agent to fully understand usage.

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 low (33%), and the description does not explain the partners or categories parameters beyond their existence. It adds no semantics that the schema does not already provide, failing to compensate for the gaps.

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 tool creates or updates a partnership ecosystem map. The verb 'Create or update' combined with the specific resource 'partnership ecosystem map' is precise and distinguishes it from siblings like createEcosystemMapSlide and createStakeholderMapSlide.

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 its many siblings. There is no mention of when it is appropriate, prerequisites, or alternatives, leaving the agent without enough context for selection.

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