inspect_project

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

No annotations provided, so the description must disclose behavioral traits. It describes what the tool inspects but does not state that it is read-only, whether it requires specific permissions, or any side effects. The description is incomplete for a tool with no annotation support.

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?

One sentence that is front-loaded with the verb and resource. It efficiently summarizes the tool's purpose without extraneous words. Highly concise.

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 simple input (one path parameter) and existence of an output schema, the description is mostly adequate. However, it lacks usage guidelines and any context on when to choose this tool over siblings, which reduces completeness.

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?

With 0% schema description coverage, the description adds value by specifying that path should point to an .aprx file. However, it does not explain other constraints like format, required extension, or absolute vs relative path, leaving gaps.

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 tool inspects an ArcGIS Pro project (.aprx) and lists the components it covers (maps, layers, data sources, layouts, default geodatabase), making the purpose specific and distinct from sibling tools like describe_data or describe_gp_tool.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for inspecting a project but does not mention prerequisites, exclusions, or compare with similar tools like describe_data.

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