update_workflow_summary

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

No annotations are provided, so the description must disclose behavioral traits. It only states it 'updates' the summary but does not mention side effects, overwrite behavior, required permissions, error handling, or what happens if the id is invalid. This is insufficient 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 brief, listing the two parameters with a short explanation each. It is front-loaded and wastes no words. However, the structure reads like a code comment rather than natural language, which could be improved.

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 large number of sibling tools, the description does not provide sufficient context for an agent to choose this tool over similar ones like 'modify_workflow'. It also fails to mention the output schema or describe the update behavior, leaving the tool's effect underdefined.

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 input schema has 0% description coverage, so the description must add meaning. It explains that 'id' can be fetched from a specific path, and 'summary' is 'preferably ReadMe'. This adds value beyond the bare schema but lacks detail on format or constraints.

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 indicates that the tool updates a workflow summary by specifying the id and summary parameters. It is clear that it targets a specific field, differentiating it from sibling tools like 'modify_workflow' which likely updates the entire workflow. However, it could be more explicit about the action.

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 provides no guidance on when to use this tool versus alternatives such as 'modify_workflow'. It does not specify context, prerequisites, or when not to use it, leaving the agent without selection criteria.

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