createEsgFrameworkSlide

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

The description mentions 'Create or update', implying mutation, but does not elaborate on behavioral traits such as whether existing slides are replaced, if data is overwritten, or permissions required. With no annotations, the description should disclose more about the tool's effects.

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 concise sentence, but it is overly terse. While not wordy, the brevity sacrifices informational content that is important for tool selection and usage.

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?

With no output schema, 4 parameters (3 undocumented), and no behavioral details, the description lacks completeness. It does not explain what the tool returns, how errors are handled, or any side effects like slide ordering.

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 25% (only _index documented). The description adds no additional meaning for the required parameters (environmental, social, governance). It does not compensate for the missing schema descriptions by explaining what each array should contain or how they map to the slide.

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 'Create or update an ESG framework summary' clearly states the verb (create/update) and resource (ESG framework summary). It distinguishes from siblings like createSwotSlide by focusing on ESG, but does not explicitly differentiate the tool's scope from other framework-related slide creators.

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 usage guidelines are provided. The description does not specify when to use this tool vs. alternatives like createBalancedScorecardSlide or createSustainabilityRoadmapSlide. There is no context on prerequisites or typical use cases.

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