get_project_schema

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

No annotations are provided, so the description carries the full burden. It openly describes the tool as a read-only retrieval of a schema and details the schema's content, including required fields and allowed values. It also clarifies that the schema is 'authoritative,' setting expectations for how the output should be used. The lack of side-effect discussion is acceptable for a getter.

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 well-structured: a concise purpose statement, an important usage note, and a compact bullet list of the schema's contents. Each sentence adds value, and the forward placement of the 'IMPORTANT' instruction ensures the agent sees the critical usage guidance early.

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 no-input tool with a defined output (a JSON schema), the description fully covers what the tool returns, what that output contains, when to use it, and why it's necessary. The presence of an output schema means the return format doesn't need over-explanation, and the description provides ample context for an agent to select and invoke the tool 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?

The tool accepts zero parameters, as indicated by the empty input schema. With no parameters to document, the description needs no parameter-level details. The baseline for 0 params is 4, and the description appropriately avoids adding irrelevant 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 clearly states 'Get the JSON schema' with a specific resource (neptune.json), using a definite verb and object. It distinguishes itself from sibling tools like deploy_project or set_secret_value by focusing on schema retrieval, not deployment or configuration mutation.

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 explicitly says 'Use this tool BEFORE creating or modifying neptune.json' and explains why (to ensure validity). It provides clear usage context, though it doesn't mention alternatives or when not to use it, which is a minor omission given the tool's unique purpose.

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