interchange_get_project_settings

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 structurally. The description adds useful scope information about what configuration surface is returned, but says nothing about behavior beyond that (e.g., live vs. serialized settings, whether editor-only).

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?

It is a single sentence, front-loaded with verb and resource, and every clause enumerates real returned content. The nested parentheticals are dense but not wasteful; it stops short of 5 only because the list of sub-settings is heavy to parse on first read.

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 usefully enumerates the settings that come back, and with zero parameters there is nothing else an agent needs in order to invoke it. It is complete for a no-arg read tool.

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 and schema coverage is 100%, so the baseline is 4. The description reinforces this by framing the call as a parameterless read of the entire project settings object.

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?

States a specific verb (Read) and a scoped resource (the project's Interchange settings / UInterchangeProjectSettings), and enumerates the concrete settings returned. It does not, however, explicitly distinguish itself from closely named siblings such as interchange_get_pipelines or interchange_get_pipeline_properties, which plausibly overlap with the pipeline-stack content described here.

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 only implies when to use it (when you want to read project-level Interchange configuration). There is no explicit when-to-use statement, no when-not-to-use, and no pointer to alternatives such as get_pipeline_properties or get_pipelines for per-pipeline inspection.

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