approvals_get_work_item_by_id

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no note on what a work item represents, whether the id is scoped to a user/tenant, or what happens on an unknown id (404 vs empty).

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?

Two short lines, front-loaded with the verb, so it is easy to scan. However, the second line is a raw endpoint path that mostly duplicates the name and annotation title rather than adding information.

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 read there is no output schema, so the description should say something about what is returned (work item type, state, approval request linkage) and clarify the undocumented 'expand' parameter. Neither is present, leaving the agent with only annotations and the name.

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 only 50%: 'id' is tagged merely as '(path)' with a uuid format, and 'expand' has no description in either the schema or the description. The description reinforces that the id identifies the item but gives no hint about what 'expand' expands or what values it accepts.

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 states a specific verb and resource: retrieve a single work item identified by its id. The 'by id' phrasing implicitly separates it from the listing siblings such as approvals_get_work_items and approvals_get_work_items_for_deployment, though no sibling is named.

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 guidance on when to use this tool versus the list endpoints or the deployment-scoped variants. The agent must infer that this is the single-item fetch from the name alone.

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