map_create

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

Annotations already declare the tool as not read-only (readOnlyHint=false) and destructive (destructiveHint=true). The description adds minimal behavioral context beyond stating it creates an item and that authentication is transparent. It does not detail side effects, permissions, or other behavioral traits.

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 concise docstring with parameter list and purpose. It is front-loaded with the action and includes a return statement. It is efficient but could be slightly more concise by removing the param details if schema descriptions existed.

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 an output schema exists (not shown), the return value line is acceptable. The description covers key parameters but lacks details on constraints (e.g., map_name uniqueness, definition structure). It is minimally adequate for a create tool.

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 schema has 0% description coverage, but the description provides meaningful parameter explanations: workspace_id (UUID), map_name, definition (auto-generated if not provided), description (optional), folder_id (defaults to root folder). This adds significant value beyond the property types and names.

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 a Map item in Microsoft Fabric. The verb 'Create' and resource 'Map item' are specific and distinct from sibling tools like map_delete, map_get, etc.

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 implies usage for creating a map but lacks explicit guidance on when to use this tool versus alternatives, or conditions for use. It mentions authentication handling but does not specify prerequisites or context.

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