get_rectangle

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

With no annotations, the description carries full responsibility. The verb 'Return' implies a read-only, side-effect-free operation, which is appropriate. However, no additional behavioral traits (e.g., authentication requirements, error conditions) are disclosed. The description is minimally adequate.

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 sentence of 12 words, efficiently stating purpose and output. It is front-loaded with the key verb and resource, achieving high conciseness without loss of essential information.

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?

While the description lists all returned properties, it does not explain the 'path' parameter. The tool is simple (2 parameters, no output schema), so the missing parameter explanation prevents full completeness. The list of returned properties compensates somewhat, but the gap remains.

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 explain parameters. It only mentions 'named Rectangle', implying 'name' identifies the rectangle, but 'path' is not explained. The agent lacks context on what 'path' represents (e.g., location in report hierarchy). This is a significant gap.

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 clearly states the action ('Return effective state'), the resource ('named Rectangle'), and lists the returned properties. It distinguishes get_rectangle from sibling get tools that target different entities (chart, dataset, textbox, etc.).

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, limitations, or when it should not be used. Among sibling get tools, no comparative advice is given.

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