slack_canvas_section_lookup

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

With no annotations provided, the description must disclose behavioral traits (e.g., read-only, permission requirements, error handling). It only describes routing through an endpoint with JWT/tenant/company scope, which is infrastructure detail, not behavioral. No mention of what happens on success/failure, rate limits, or side effects.

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 but includes routing details that are not essential for tool usage (e.g., '/api/tools/invoke' scope). It could be more focused on the tool's function. However, it is not excessively long or redundant.

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 tool's simplicity (one parameter, output schema exists), the description is incomplete. It does not state the tool's purpose, required arguments, or return value. The output schema exists but is not referenced to supplement the description. The agent is left with little context to use the tool correctly.

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 single parameter 'arguments' (string, default '{}') has 0% schema description coverage. The description adds 'JSON string of arguments for the connector operation', which tells the type but not the structure or required keys. For such a sparse schema, the description should provide more detail (e.g., example keys like canvas_id, section_id).

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 calls it a 'Slack connector operation' without stating what it does (look up a canvas section). The name implies retrieval, but the description fails to specify the action or resource. Sibling tools like slack_create_canvas, slack_edit_canvas, and slack_delete_canvas are distinguishable by name, but the description provides no differentiation beyond the generic connector operation.

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 on when to use this tool versus alternatives like slack_access_canvas or slack_get_channel_history. The description does not mention prerequisites, context, or exclusions, leaving the agent to guess applicability.

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