get_project_info

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 covered. The description adds real value beyond that by disclosing the data source is the in-memory project defaults rather than a saved asset, and that every returned string may be empty - a nuance an agent needs before treating a value as authoritative.

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 purpose sentence is front-loaded and efficient, but the field list is stated twice - once as prose ('Returns project_name, project_version, ... as strings that may be empty') and again as an object literal - which is genuine redundancy. The near-identical repeated listing costs space without adding information.

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 no output schema, the description carries the burden of describing return values and does so completely: it enumerates all ten fields with their types and warns they may be empty. The only meaningful omission is any hint about where this data originates if defaults are unset, but for a zero-argument read of project settings this is close to complete.

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 no parameter semantics to document and the baseline is 4. The description correctly adds nothing spurious here, though the enumerable return fields are return-value information rather than parameter information.

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 concrete verb and resource ('Read the project metadata from the in-memory UGeneralProjectSettings defaults') and even names the backing object, so an agent knows exactly what is being read. It does not, however, distinguish itself from closely related siblings such as get_project_settings_value or list_project_setting_sections, which read project settings by section/key.

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 explicit when-to-use statement and no named alternative. Nothing tells the agent to prefer this over get_project_settings_value when it needs a specific settings key rather than the ten fixed metadata fields, so selection depends entirely on inferring from the field list.

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