md_project_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Read' implies a non-destructive operation, but the description does not mention error behaviors, permission requirements, or side effects. For a simple read operation, the read-only nature is somewhat transparent, but more detail could be expected.

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 a single, front-loaded sentence that contains no superfluous information. It is appropriately concise for the tool's simplicity, earning its place without waste.

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?

While the output schema likely documents return values, the description lacks context about the project lifecycle (e.g., whether the project must already be initialized) and the nature of the manifest. Given the tool's simplicity and the presence of an output schema, the description is minimally adequate but leaves gaps in workflow understanding.

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 description does not explain the 'project_directory' parameter or its expected format; it only appears in the schema with a title. With 0% schema description coverage, the description should compensate by clarifying how the directory is used or validated, which it does not. The agent is left to infer that it is a filesystem path.

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 reads a pipeline project's manifest, using a specific verb ('Read') and a distinct resource ('pipeline project's manifest'). This distinguishes it from sibling tools like md_pipeline_get_config (reads config) and project mutation tools. The purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. It only states the core action, leaving the agent to infer usage. No sibling alternatives or contextual triggers are mentioned.

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