read_prompt

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

No annotations provided, and description adds no behavioral detail beyond the basic retrieval operation. It does not disclose authentication needs, rate limits, or side effects, though read operations are generally safe.

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?

Single sentence is concise and front-loaded, but the extreme brevity sacrifices necessary information about parameters and usage context.

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?

Given 3 parameters, no schema descriptions, and an output schema that may document returns, the description does not adequately explain optional parameters or distinguish this tool from sibling retrieval tools like list_prompts.

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 description coverage is 0%, and description only mentions 'prompt id' but fails to explain the optional project_id and location_id parameters. This provides little additional meaning beyond parameter names.

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?

Description clearly states 'get the prompt content with given prompt id', specifying verb (get) and resource (prompt content). It distinguishes from sibling tools like create_prompt, delete_prompt, list_prompts, update_prompt.

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?

Description implies use for retrieving prompt content by ID, but offers no direct guidance on when to use this tool vs alternatives like list_prompts or search, and no exclusions or prerequisites.

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