Get project defaults

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds meaningful behavioral insight beyond annotations by explaining the 'source' field's three possible values (explicit, derived, fallback), which clarifies how the data is computed rather than merely stored.

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 efficient sentence that conveys the resource, verb, scope, response fields, and semantic of the 'source' value. It's appropriately compact with no filler, though the enumeration of source values is slightly dense and could be structured more cleanly.

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 single-parameter read-only tool with 100% schema coverage and clear annotations, the description is largely complete. It explains the response semantics adequately. However, it doesn't note any pagination or mention what an empty/absent defaults response looks like, which is a minor gap for a tool this simple.

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?

Schema coverage is 100%, so the schema documents the sole project_id parameter fully, including its pattern. With only one parameter fully specified, the baseline is 3, but the description adds value by confirming the parameter selects the project whose defaults are being read, reinforcing the project-scoped nature without contradicting the schema.

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 specific verbs and resources ('Get the effective rank-check schedule and SERP market defaults for a project') and clearly distinguishes this read tool from the sibling update_project_defaults. It names the specific response elements (serp_depth, serp_stop_on_match, source) which makes the tool's purpose concrete and identifiable.

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 clearly indicates it reads defaults for a project and explains the 'source' field semantics (explicit/derived/fallback), giving useful context for when to consult this tool. However, it doesn't explicitly contrast against update_project_defaults or get_project, leaving the usage boundaries implied rather than stated.

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