Get resume master field

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

With no annotations, the description carries the burden of disclosing behavior. It states the operation is a read, scopes access to one file, and describes the nature of the data ('stable resume facts'). It does not explain error behavior or return characteristics for invalid paths, but for a simple read tool the provided context is adequate.

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 two sentences, front-loads the verb and resource, and every element adds value. It is concise without being under-specified, including examples and a usage hint without unnecessary filler.

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?

This is a simple single-parameter read tool. The description includes the file name, path format with examples, scope limitation, and guidance for an alternative tool, making it sufficiently complete without an output schema or complex annotations.

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 schema covers the path parameter with one example. The description adds multiple examples ('skills', 'projects[0].description') and clarifies the dot/bracket path syntax, providing additional meaning beyond the schema description.

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 one field from resume_master.json using a dot/bracket path. It uses a specific verb ('Read') and resource ('resume_master.json'), and the examples distinguish it from sibling tools like update_resume_master_field and list_resume_master_structure.

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 advises using list_resume_master_structure first if unsure of the path, providing an alternative for a specific scenario. It also notes the tool is scoped to one file, but it does not explicitly contrast with the update sibling or clarify when a list/read of the entire file would be more appropriate.

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