slack_sdlc_canvas_template_id

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

The description adds some useful context beyond annotations: routing is restricted to the governed connector authority, and the read effect is required and verified by Spring. It does not contradict the readOnlyHint or destructiveHint annotations. However, it does not describe return behavior or other runtime characteristics, and the approval_ref write-resume note is mildly misleading for a read-only 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 compact and well-structured: one routing sentence followed by a labeled Args list. The main redundancy is restating the operation name and platform tool path in the same opening sentence, but the rest is efficient and easy to parse.

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?

Despite having an output schema and decent parameter descriptions, the core behavior of the tool is never stated in plain terms: what an SDLC canvas template ID is, when to request it, and what the caller receives. For a tool with an opaque noun-based name, the description must say it reads or returns the template ID; instead it only restates the operation name and its routing constraint. This leaves too much ambiguity for tool selection among hundreds of siblings.

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%, but the prose compensates by giving a semantic line for every parameter: arguments is a JSON string, project_id is an authenticated UUID, project_ref is an exact correlation reference, connector_account_ref is a bound alias, idempotency_key is a stable identity, and effect must be read. This is valuable, though the arguments parameter remains opaque about expected contents and approval_ref's write framing is confusing.

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 opening line merely restates the tool's name and platform path ('Slack connector operation sd...`...`), and the following sentence about routing is a governance constraint, not a purpose statement. The description never says what the operation actually does, e.g., retrieves or returns an SDLC canvas template ID. An agent cannot confidently distinguish this from other Slack canvas 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 explicit when-to-use or alternative guidance is provided. The only operational constraint is that calls route through the exact project/account governed connector authority and that effect must be read, but there is no statement about when to choose this tool over siblings like slack_access_canvas or slack_canvas_section_lookup. Approval_ref's 'when resuming a write' is also confusing for a read-only operation.

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