Project Summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only generic filler ("返回可验证的结构化结果", path/write limits depend on service capability) that offers little concrete behavioral detail beyond what the annotations already provide.

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 definition is short and front-loads the purpose, which is good. However, the second half is generic boilerplate about structured results and service-capability limits that does not earn its place given the missing parameter and usage 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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. But for a 2-parameter tool with 0% schema description coverage and no usage guidance, the description is too thin: an agent cannot tell what aprx_path expects or when this summary is the right call.

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 never mentions either parameter. It does not explain that aprx_path must point to an .aprx project file, nor what max_broken_list controls (the cap on reported broken sources). With two undocumented parameters and no compensating narrative, the definition leaves parameter meaning entirely to inference.

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 gives a clear verb+resource ("读取摘要工程" = read the project summary) that matches the tool name and title. It does not, however, distinguish this tool from close siblings like arcgis_pro_list_projects or arcgis_pro_project_connections, so an agent must infer the distinction from the name alone.

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 versus alternatives, nor any prerequisites (e.g., a project must be open, or that a specific .aprx path is required). The only conditional sentence ("写入和路径限制以服务能力为准") is about service capability limits, not usage selection.

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