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

Annotations already declare readOnlyHint and idempotentHint; the description adds concrete behavioral context by specifying that it parses the .xcscheme file and that build/run/test configs plus env/launch arguments are returned 'where present'. No contradiction with annotations.

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 description is compact and front-loaded, with a summary sentence followed by focused parameter and return sections. It is slightly redundant in using a heading that repeats the tool name, but no sentence is wasted.

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?

For a simple read-only inspection tool with two required parameters and no output schema, the description covers inputs, source file, and return content. Combined with the annotations, an agent has everything needed 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?

Input schema coverage is 0%, so the description carries the full burden. It successfully explains both parameters: projectPath as the path to the .xcodeproj/.xcworkspace and scheme as the scheme name to inspect, which is sufficient for selection and invocation.

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 uses a specific verb ('Parse and display') with a concrete resource (an Xcode scheme's build, run, and test configurations from its .xcscheme file), which clearly distinguishes it from build/test/list siblings. The title reinforces but the body adds enough detail to identify the tool's unique purpose.

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 read-only inspection context is clear: an agent should call this when it needs an Xcode scheme's configuration rather than to build, test, list, or manipulate a project. It does not explicitly name alternatives like xcodebuild-get-details or state when not to use it, but the purpose sentence makes the appropriate use case evident.

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