is_square

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

The description does not disclose the return type or behavior for edge cases (e.g., negative numbers, zero). As annotations are absent, the description should clarify what 'Test' means (e.g., returns true/false).

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, front-loaded sentence that efficiently communicates the tool's function without unnecessary detail.

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 tool with one parameter and an assumed output schema, the description is minimally adequate. However, it lacks clarity on the return value and does not address potential edge cases, which a more complete description would include.

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 parameter 'n' is described in the schema as 'Integer.', and the description adds no additional meaning. With 100% schema coverage, the description should provide more context, such as allowed range or special values.

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 verb 'Test' and the resource 'perfect square', making the purpose unambiguous. It distinguishes from siblings like 'sqrt' and 'ispower' by focusing on the specific boolean test for squareness.

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 is given on when to use this tool versus alternatives like 'ispower' or 'sqrt'. The description does not provide context for optimal usage or exclusions.

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