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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds one genuine piece of context beyond that — results are drawn from privacy-filtered project metadata — but says nothing about freshness, polling behavior, or what states an execution can be in.

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?

It is a single short sentence, which is appropriately sized, but the wording 'Read hosted get ...' is redundant and awkward rather than economical. Brevity here comes partly from under-specification, not tight authoring.

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 simple one-parameter read tool with a fully documented schema and complete annotations, the description is minimally adequate. It lacks any statement of what the returned status represents or when the call is appropriate, and no output schema exists to fill that gap.

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 100% and the single executionId parameter is already documented thoroughly, including the disambiguation 'not a session or project ID'. The description adds no additional parameter meaning, so the baseline 3 applies.

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 does convey the resource (agent execution status) and an action (read), so an agent can guess the intent. But the phrasing 'Read hosted get agent execution status' is garbled and tautological, and it never distinguishes this tool from close siblings such as begin_agent_execution, finalize_agent_execution, record_agent_execution_activity, or get_project_status.

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?

There is no when-to-use guidance, no prerequisite (e.g. that an execution must have been started via begin_agent_execution), and no mention of alternative tools for adjacent needs. The only hint is the param note in the schema, not the description.

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