canvases_sections_lookup

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

No annotations are provided, so the description must disclose behavior. It only implies a read operation but does not state whether the tool is safe (non-destructive), idempotent, or requires specific permissions. Important behavioral traits like pagination, authorization, or side effects are omitted.

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 a single short sentence, which leads to under-specification. While concise, it sacrifices completeness. Key details about parameters and behavior are missing, making it inadequate for the tool's complexity.

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 has two required parameters (one a free-form object) and no annotations, the description should provide richer context. It does not explain how criteria work, what outputs look like (despite having an output schema), or any usage constraints. The description is insufficient for complete understanding.

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?

With 0% schema description coverage, the description should explain parameter roles beyond field names. It mentions 'criteria' for matching but does not specify allowed properties, structure, or examples. The canvas_id parameter is not described at all. The description adds minimal semantic value.

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 the tool finds sections matching criteria in a canvas, using a specific verb ('Find') and resource ('sections'). It clearly distinguishes from sibling canvases tools (e.g., canvases_create, canvases_edit) by specifying 'sections' and 'lookup' 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 search tools or other canvas section operations. There is no mention of prerequisites, when not to use, or preferred contexts.

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