get_arcgis_info

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

No annotations are provided, so the description carries the full burden, but for a zero-parameter read of local application metadata the risk surface is small. It does disclose the categories of data returned (version, licence, extensions, project path), which implicitly signals a non-mutating information fetch, but it never explicitly states that it is read-only or side-effect free.

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?

A single compact sentence that front-loads the most salient fact (ArcGIS Pro version). It is efficient with no filler, though the terseness comes at the cost of the verb and any usage framing.

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?

With zero parameters and an output schema present, the description does not need to enumerate return fields or formats. It states the scope of what is inspected (Pro installation plus current project path), which is sufficient for an agent to call 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. No parameter-level details are missing or needed.

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 names the specific resources returned (version, licence level, extensions, project path), which is more than a tautology. However, it is a noun phrase with no verb and it does not distinguish this tool from nearby siblings such as get_project_info, get_capabilities, get_environment, or diagnose, all of which plausibly overlap with 'current environment info'. An agent must guess which of these to call.

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?

There is no statement of when to use this tool, no exclusions, and no named alternative. Given that get_project_info and get_capabilities appear in the same sibling list, the absence of routing guidance is a real gap rather than a trivial omission.

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