asana_update_section

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

The description simply says 'Rename a section,' which adds no behavioral context beyond the operation itself. Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the bar for additional disclosure is lower, but the description fails to add any nuances such as how the rename affects viewers or whether permissions are required.

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 extremely concise and front-loaded with the core action. It has no fluff or redundant information. However, its brevity borders on under-specification, which slightly detracts from appropriate sizing for a complete tool definition.

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 simplicity of the tool (two parameters, no output schema), the description is minimal but leaves the agent without necessary context such as the fact that section_gid identifies an existing section, that name is the updated title, and what response to expect. With no schema description coverage and no output schema, the description should provide more context to ensure correct invocation.

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 for the lack of parameter documentation. However, the description only says 'Rename a section' and does not clarify that section_gid is the identifier of the section to rename or that name is the new name. The parameter names are somewhat self-explanatory, but the description provides no explicit mapping or additional meaning.

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 states a specific verb ('rename') and a clear resource ('a section'), and it distinguishes this tool from siblings like asana_create_section, asana_delete_section, asana_move_section, and asana_reorder_section. Even though the description is minimal, 'rename' precisely conveys the action and scope.

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 guidance on when to use this tool versus alternatives. It does not mention that this should be used specifically for renaming, nor does it exclude cases better served by other section-related tools. No contextual or exclusions are provided.

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