find_cell

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Find' implies a read-only lookup, but the description does not state what happens when the cell is not found, whether the search is recursive across the whole diagram, or what output the agent should expect.

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 an 11-word sentence with no wasted words. It front-loads the action and resource while staying immediately parsable.

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?

For a simple two-parameter lookup, the description is usable, but there is no output schema, no annotations, and no usage routing to alternatives. Return format and error behavior are left unspecified, which makes the description adequate yet incomplete.

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 already describes both parameters with 100% coverage, including plain descriptions for xml_content and cell_id. The description adds little beyond identifying cell_id as the lookup key, which is already evident from the schema.

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?

States a precise operation — find a specific cell by ID — on a clear resource, a Draw.io diagram. The 'specific... by ID' qualifier distinguishes it from list_cells, which would return cells more generally.

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 intended use is implied: call this when you have a cell_id and need that specific cell from XML content. However, it does not explicitly say when to use this tool instead of siblings like list_cells or when not to use it.

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