get_data_info

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

No annotations are present, so the description must disclose behavioral traits. It says nothing about what the tool does, returns, or any side effects. The deprecation notice is the only behavior mentioned, but it does not describe the tool's actual operation.

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: 'Deprecated: use data_inspect.' It is concise and every word earns its place, clearly indicating the tool's status and providing a replacement. No wasted text.

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 tool's four parameters and an output schema, the description is severely incomplete. It fails to describe the tool's function, expected inputs, or return values. Even though deprecated, an agent could still encounter this tool and needs more context to use or avoid it correctly.

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%, and the description provides no information about parameters. With four parameters, including 'data_path', 'vars_list', and 'project_path', the description must compensate but does not add any meaning 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?

The description does not state what the tool does beyond its name, 'get_data_info'. It only says 'Deprecated: use data_inspect,' which directs users away but does not clarify the tool's function. This is not a tautology, but it fails to specify a verb and resource.

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 explicitly says 'use data_inspect,' providing a clear alternative and indicating when not to use this tool. This is direct, unambiguous usage guidance that distinguishes the tool from its replacement.

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