read_context

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

Annotations (readOnlyHint, openWorldHint, destructiveHint) already cover the safety profile. The description adds value by disclosing what the tool returns (context contents) and the behavior of the no-argument mode (global context). This goes beyond the annotations and gives the agent an accurate picture of the operation without contradicting any annotation.

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 dense sentence that front-loads the core purpose and enumerates the return contents in a compact list. Every clause contributes meaning—parameter scoping, examples, and global fallback—with no filler or redundancy. It is appropriately sized for the complexity.

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?

The description covers the main return contents and the no-argument behavior, which is sufficient for basic invocation. However, it leaves the 'acid' parameter completely undocumented, provides no output schema, and doesn't address how multiple parameter groups interact (e.g., ids vs. teamIds). For a read-only tool with optional params these gaps are notable but not fatal.

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 only 25% (only 'ids' is described). The description partially compensates by mapping 'entity ids' to ids, and 'projects and teams' to projectIds/teamIds, which clarifies those three parameters. However, the 'acid' parameter is entirely unexplained in both the schema and description, leaving a significant semantic gap for a low-coverage definition.

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 'Targetprocess Context' and enumerates its contents: processes, practices, terms, custom field definitions, selected projects/teams, logged user, version. It also specifies the scope based on arguments (entity ids vs. projects/teams vs. global). While it doesn't explicitly contrast with sibling read tools, the name and content make the purpose unambiguous.

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 implies usage: pass ids, teamIds, projectIds, or nothing for global context. However, it provides no explicit guidance on when to choose this over siblings like read_meta, read_get, or read_query, and no exclusions. The 'Without arguments' clause gives a hint of a fallback mode, but the when-to-use guidance is largely left to inference.

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