list_workspace_templates

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

Given no annotations, the description must disclose behavioral traits. It only describes return fields but does not explicitly state that the operation is read-only, nor does it mention side effects, authentication requirements, or rate limits. The description is insufficient for transparency.

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 short and includes an Args/Returns block. The main purpose sentence is front-loaded. However, there is redundancy in restating the parameter in both the description and schema. It could be more concise by removing the duplicate information.

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?

The description lacks completeness. It fails to clarify the parameter requirement contradiction, does not elaborate on the return structure beyond listing field names, and provides no context about when the list is empty or fails. Given the output schema exists, more detail on return values would be expected.

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 description labels 'caller_agent_id' as '必須' (required) but the schema marks it as optional (default null). This contradiction is confusing. The description adds minimal meaning beyond the schema, only stating it's the caller agent ID, which is obvious from the name. With 0% schema coverage, more explanation is needed.

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 '利用可能なテンプレート一覧を取得する' which means 'Retrieve a list of available templates.' The verb 'list' matches the tool name, and it distinguishes from the sibling 'get_workspace_template' which retrieves a single template. However, it does not explicitly differentiate from other list tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_workspace_template'. There is no mention of prerequisites, context, or when not to use. The description lacks any usage recommendations.

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