sympy_integer

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Create Integer,' which implies a constructor but does not clarify if there are side effects, validation, or return type expectations (though output schema exists).

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?

While extremely concise at two words, the description is under-specified and fails to add meaningful information. It does not earn its place as it adds no value beyond the name.

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 presence of an output schema, the description need not detail return values. However, the lack of annotations and minimal description leaves the tool incomplete for an agent needing to differentiate from many similar sibling tools.

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 has one required string parameter 'n' with 0% description coverage. The description does not explain what 'n' represents (e.g., numeric string, variable name) or how it should be formatted, leaving the agent without critical context.

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 'Create Integer.' is nearly a tautology of the tool name 'sympy_integer'. It provides a verb and resource but no additional context about what kind of integer (e.g., SymPy integer vs Python int) or how it differs from sibling tools like sympy_float or sympy_rational.

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 provided on when to use this tool over alternatives. With many sibling tools for creating numbers (e.g., sympy_float, sympy_rational, sympy_symbol), the agent has no basis to choose this one.

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