get_cop_geometry

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

With no annotations and no output schema, the description carries the full behavioral burden, yet says nothing about read-only safety, whether the geometry is returned inline vs by reference, size/pagination concerns, or the return format. Only the bare retrieval intent is conveyed.

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 core purpose is front-loaded in a single efficient sentence. The trailing Args block is somewhat redundant with the schema but stays short, so there is little waste.

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 tool that returns geometry data with no output schema to explain the return shape, no annotations for safety, and 0% parameter coverage, the description is far too thin to let an agent call it confidently or interpret results.

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%, so the description must compensate, but its Args block merely restates the parameter titles ("Path to the COP node", "Output connector index") with no added syntax, format, or default-value meaning. Nearly zero value beyond 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 specific verb+resource ("Get geometry representation from a COP node"), which is clearer than a tautology. However, "geometry representation" is vague about what form the data takes, and it offers no differentiation from close siblings like get_cop_layer, get_cop_vdb, or get_cop_info, which also read COP node data.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_cop_layer or get_cop_vdb. The agent must guess which COP-data reader is appropriate.

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