Create Shape With Text

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions creation and the text label but does not disclose side effects, permissions, reversibility, return values, or whether existing text is overwritten. For a mutation tool, this is a significant gap.

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 concise and front-loaded, with the core action in the first sentence and useful examples in the second. It avoids fluff, though the second sentence is fragmentary. It earns its place with minimal waste.

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?

This tool has four parameters including a nested object, no annotations, and no output schema. The description is too sparse to compensate, lacking details on props, parentId usage, supported shape list completeness, and any behavior after creation. An agent would need additional context to invoke this correctly.

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 0%, so the description must compensate. It lists some shapeType values, adding value there, but does not explain parentId, text, or props. These parameters are left underspecified, and the nested props object is not described at all, making it hard for an agent to pass correct arguments.

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 verb 'Create' and the resource 'shape with built-in text label', distinguishing it from create_node or set_text. The addition of shapeType examples further clarifies the tool's scope, making its purpose unambiguous.

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 gives no explicit guidance on when to use this tool versus alternatives like create_node or set_text. It implies usage for shapes with text labels but does not state exclusions or mention when to prefer another tool, leaving the agent without decision guidance.

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