format_title

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It lists the modifiable title properties but does not explain whether unspecified properties are left unchanged, whether values overwrite existing settings, or any side effects. This is minimal transparency for a mutation tool.

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 sentence that is front-loaded with the core purpose and includes all key parameters. It is concise with zero wasted words.

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?

For a relatively simple tool, the description is adequate but has gaps. It lacks mention of behavior for absent parameters, prerequisites, or return values. Given no annotations and no output schema, the description could be more complete, but it covers the essential formatting scope.

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 coverage is only 25%, so the description must compensate. It adds meaning by clarifying 'font size' for size, 'colour' for color, and listing alignment values (left|center|right). However, it does not explain value formats for text, size, or show, nor the meaning of null defaults, providing only partial compensation.

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 formats a visual's title and lists the specific properties (text, color, font size, alignment, show/hide). It is specific about the resource and action, but does not explicitly distinguish it from sibling tools like set_visual_title or style_visual.

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 formatting visual titles, but provides no explicit guidance on when to use this tool versus alternatives. No exclusions or alternative tool references are mentioned, making the usage merely implied.

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